Load Balancer Explained: How It Works

A Load Balancer distributes incoming network traffic across multiple servers instead of sending every request to a single server. This helps prevent server overload, improves application performance, and keeps services available even when individual servers fail.
Load balancing is a key part of modern cloud infrastructure, especially for applications that handle thousands or millions of requests.

⚙️ How Does a Load Balancer Work?​

A Load Balancer sits between clients and backend servers. When a user sends a request, the Load Balancer receives it and selects an appropriate server based on its configuration, routing algorithm, and server health.
The process works like this:

1. A client sends a request to the Load Balancer.
2. The Load Balancer evaluates available backend servers.
3. It selects a server based on the configured algorithm.
4. The request is forwarded to that server.
5. The server processes the request and returns the response.

Example:
Imagine an application running on three backend servers:

• Server 1
• Server 2
• Server 3

Instead of sending all incoming requests to Server 1, the Load Balancer distributes them across the three servers to avoid overloading a single machine.

---

🔄 Common Load Balancing Algorithms​

A Load Balancer can use different algorithms to decide which server should receive each request.

Algorithm	How It Works
Round Robin	Distributes requests sequentially across available servers.
Least Connections	Sends new connections to the server with the fewest active connections.
Least Response Time	Selects a server based on response time and other supported performance metrics.

The best algorithm depends on the application, server capacity, and traffic patterns.

---

🩺 What Are Health Checks?​

Health Checks allow a Load Balancer to monitor backend servers and determine whether they are healthy enough to receive traffic.
Common health check methods include:

• HTTP Checks: Send HTTP requests to verify that an application endpoint is responding correctly.
• TCP Checks: Check whether a server accepts connections on a specific port.

If a server fails its health checks, the Load Balancer stops routing new traffic to it and sends requests to healthy servers.
Once the failed server becomes healthy again, it can be added back to the available server pool.

---

🚀 Benefits of Using a Load Balancer​

Load balancing provides several important benefits:

• Scalability: Distributes traffic across multiple servers and makes it easier to add more capacity.
• High Availability: Helps keep applications accessible when one or more backend servers fail.
• Reliability: Reduces the impact of individual server failures.
• Performance: Prevents traffic from overwhelming a single server.

---

☁️ Types of Load Balancers in AWS​

Amazon Web Services (AWS) provides four main types of Elastic Load Balancers (ELB).
1. Classic Load Balancer (CLB)
The older generation of AWS load balancing. Supports basic Layer 4 and Layer 7 load balancing.
2. Application Load Balancer (ALB)
Operates at Layer 7 (Application Layer). Supports content-based routing using HTTP headers, hostnames, URL paths, and other request attributes.
3. Network Load Balancer (NLB)
Operates primarily at Layer 4 (Transport Layer). Designed for high-performance TCP, UDP, and TLS traffic.
4. Gateway Load Balancer (GWLB)
Operates at Layer 3 and helps deploy and scale virtual network appliances, such as firewalls and intrusion detection systems.

---

📌 Load Balancer vs. a Single Server​

Single Server	Load Balancer
Handles all incoming traffic itself.	Distributes traffic across multiple servers.
Can become a bottleneck.	Reduces pressure on individual servers.
Server failure can interrupt the service.	Can redirect traffic to healthy servers.
Scaling may require upgrading one machine.	Supports horizontal scaling by adding servers.

Important: A Load Balancer does not automatically guarantee high availability. The backend servers, health checks, network configuration, and Load Balancer deployment must all be designed properly.
In cloud platforms like AWS, Elastic Load Balancing is a managed service designed to distribute traffic across multiple Availability Zones, rather than relying on a single standalone server.

---

❓ Frequently Asked Questions​

---------------------

1. Is a Load Balancer a hardware device or software?​

It can be either. Load Balancers can run as physical appliances, software applications, or managed cloud services such as AWS Elastic Load Balancing.

2. Does a Load Balancer increase server performance?​

It does not make an individual server faster. Instead, it distributes workloads across multiple servers, helping the overall application handle more traffic.

3. What happens if a backend server goes down?​

The Load Balancer detects the failure through health checks and stops sending new requests to that server, provided healthy alternatives are available.

4. What is the difference between ALB and NLB in AWS?​

ALB handles application-level traffic at Layer 7 and supports advanced HTTP routing. NLB operates primarily at Layer 4 and is designed for high-performance network traffic.