What Is a Load Balancer?
A load balancer sits between users and your application servers. Instead of sending every request to one server, it distributes requests across multiple servers.
Think of the coffee-shop employee directing customers to different counters. The employee does not prepare the coffee—the employee simply makes sure no single counter becomes overloaded.
Learn more about load balancing explained: a simple real-world story.
Why Does Load Balancing Exist? The Problem It Solves
Suppose your application has one server and suddenly 10,000 users visit it. The server may become slow or even crash. Adding more servers helps, but users still need a way to reach those servers efficiently.
This is where the load balancer helps.
Where Load Balancing Executes and How Data Flows
The load balancer sits between clients and servers. It receives incoming requests and routes each to one of the available servers based on a chosen algorithm, ensuring balanced workload distribution. Client Request Load Balancer Server 1 Server 2 Server 3
Client Request
Load Balancer
Server 1
Server 2
Server 3
How Does It Choose a Server?
Load balancers can use different algorithms.
Round Robin sends requests to servers one after another.
For example:
Request 1 → Server 1
Request 2 → Server 2
Request 3 → Server 3
Request 4 → Server 1
Least Connections sends new traffic to the server currently handling the fewest active connections.
Some systems also use weighted routing, IP-based routing, or other rules.
Popular Load Balancing Tools
You usually do not need to build a load balancer yourself. Popular options include AWS Elastic Load Balancing, NGINX, HAProxy, Google Cloud Load Balancing, Azure Load Balancer, and Cloudflare.
Summary
Load balancing is essential for distributing workloads efficiently across servers, enhancing performance, reliability, and scalability. Understanding its operation, appropriate use cases, and pitfalls helps engineers design robust systems. By applying best practices and considering trade-offs, load balancing becomes a powerful tool in modern system architecture.
Key Takeaways
- Load balancing distributes traffic to prevent server overload and improve system reliability.
- It operates at various layers with different routing algorithms and health checks.
- Proper configuration, including session persistence and security, is critical.
- Load balancing introduces trade-offs between complexity, latency, and scalability.
- Use load balancing when scalability and availability needs justify its overhead.
Frequently Asked Questions
What are the common load balancing algorithms?+
Common algorithms include Round Robin, Least Connections, IP Hash, and Weighted Round Robin. Each has different strategies for distributing traffic based on server load, connection counts, or client IP.
Can load balancers handle SSL/TLS encryption?+
Yes, many load balancers support SSL/TLS termination, decrypting incoming traffic before forwarding it to backend servers, which reduces server load and centralizes certificate management.
What is session persistence in load balancing?+
Session persistence, or sticky sessions, ensures that a client’s requests are consistently routed to the same backend server, which is important for stateful applications.
How do load balancers detect unhealthy servers?+
They perform periodic health checks, such as HTTP requests or TCP pings, to verify server responsiveness and exclude unresponsive servers from the pool.