Definitions are often difficult to understand. I think you just need an explanation to use them.
Brief explanation: load balancing is one of the functions of the reverse proxy, and the reverse proxy is one of the software tools that can perform load balancing.
And the long explanation below is explained.
For example, your company’s service has customers in the UK and in German. Since the policies are different for the two countries, your company has two web servers, uk.myservice.com for the UK and de.myservice.com for German, each with a different business logic. In addition, your company wants only one single endpoint for this service, myservice.com. In this case, you need to configure the reverse proxy server as a single endpoint. The proxy server accepts the url myservice.com and rewrites the URL of incoming requests so that requests from the UK (defined by the ip source) go to uk.myservice.com and requests from the German language go to de.myservice.com. From a UK client’s point of view, he never knows that the answer is indeed created on uk.myservice.com.
In this case, loading the request traffic to the service is actually balanced for the servers on uk.myservice.com and de.myservice.com as a side effect. Thus, we usually do not call it used as a load balancer, we simply say it as a reverse proxy.
But let's say whether your company uses the same policy for all countries and has 2 servers, a.myservice.com and b.myservice.com, only for the reason that the workload is heavy for one server. In this case, we usually refer to the reverse proxy server as a load balancer to emphasize the reason it is used.
source share