Client Side Load Balancer vs Server Side Load Balancer
Client Side Load Balancer |
Server-Side Load Balancer |
---|---|
If you are keeping the load balancer on the client side and giving the load balancing responsibility to the client, then it’s called Client-Side Load Balancing. | If you are keeping the load balancer on the server side and giving the load balancing responsibility to the server, then it’s called Server-Side Load Balancing. |
No more single point of failure in Client Side Load Balancer. | The main disadvantage of Server-Side Load Balancing is the single point of failure. |
Less network latency as the client can directly call the backend servers. | Network latency rises in Server-Side Load Balancing. |
Cost Reduction as there is no need for server-side load balancing. | The cost is high to implement Server-Side Load Balancing in comparison to Client-Side Load Balancing. |
In this case, the microservice code is combined with the load balancer’s logic. | Since each microservice will have a particular load balancer, the complexity of the system rises and it is hard to manage. |
Client-Side Load Balancer Provided by Spring Cloud: Spring Cloud Load Balancer, Netflix Ribbon | Server-Side Load Balancer Provided by Spring Cloud: Spring Cloud Gateway, Netflix Zuul |
Spring Cloud – Difference Between Client Side and Server Side Load Balancer
Spring Cloud is a collection of projects like load balancing, service discovery, circuit breakers, routing, micro-proxy, etc will be given by Spring Cloud. So spring Cloud basically provides some of the common tools and techniques and projects to quickly develop some common patterns of the microservices.
Contact Us