advancedAPI Gateway & Service Communication

Why is client-side load balancing (each service instance discovering peers itself) sometimes preferred over a centralized load balancer?

A centralized load balancer is a single hop every request must pass through, adding latency and becoming a potential bottleneck/single point of failure at scale. Client-side load balancing (via a service registry like Eureka) lets each caller query the registry once and then call instances directly, spreading the discovery load and removing the extra network hop per request.

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Sign in to generate a response

Next Step

Continue to Why is Docker Compose useful for local development of a multi-service Spring Boot app even though production uses Kubernetes?← Back to all Spring Boot questions