What is load balancing and why is it important?

Question

Accepted Answer

**Load balancing** distributes incoming requests across multiple servers — enabling horizontal scaling, improving availability, and preventing any single server from being overwhelmed. It's a fundamental component of scalable, reliable systems.

## What a load balancer does

```text
A LOAD BALANCER sits in front of multiple servers and distributes requests among them:
  Client → LOAD BALANCER → ┬→ Server 1
                           ├→ Server 2
                           └→ Server 3
  → spreads load → no single server is overwhelmed (enables HORIZONTAL scaling)
  → routes around FAILED servers (health checks) → high AVAILABILITY
  → a single entry point for clients
```

## Why load balancing matters

```text
✓ SCALABILITY → distributes load across many servers → handle more traffic by adding servers
✓ AVAILABILITY → if a server fails, route to healthy ones → no single point of failure
✓ PERFORMANCE → prevents any server from being overloaded → consistent response times
✓ Enables ZERO-DOWNTIME deploys, maintenance (take servers out of rotation)
→ a foundation of scalable, highly-available systems.
```

## Load balancing algorithms

```text
ROUND ROBIN → requests distributed in turn (simple, common)
LEAST CONNECTIONS → to the server with the fewest active connections (load-aware)
WEIGHTED → distribute by server capacity (bigger servers get more)
IP HASH / sticky sessions → route a client consistently to the same server (for stateful)
→ choose based on the workload (round robin / least connections are common defaults)
```

## Why it matters

Understanding load balancing is foundational because it's a **fundamental component of scalable, reliable systems**, so it's essential system-design knowledge.

A load balancer distributes requests across multiple servers, which addresses two core needs: **scalability** (spreading load so the system can handle more traffic by adding servers — enabling horizontal scaling, which load balancing makes possible) and **availability** (routing around failed servers via health checks, so no single server is a point of failure).

Understanding **why it matters** — scalability (distributing load to handle more traffic), availability (surviving server failures), performance (preventing overload for consistent response times), and enabling zero-downtime deployments and maintenance (taking servers out of rotation) — clarifies its central role in scalable, highly-available systems.

Load balancing works hand-in-hand with horizontal scaling and stateless services to build systems that scale and stay available, making it a recurring, fundamental concept in system design.

Understanding the **algorithms** — round robin (simple, common), least connections (load-aware), weighted (by capacity), and IP hash/sticky sessions (for stateful routing) — provides practical knowledge of how load is distributed.

Since load balancing is essential to scalable, reliable systems (enabling horizontal scaling and high availability by distributing requests and routing around failures), and since understanding what it does, why it matters, and how it distributes load is fundamental to system design, understanding load balancing is essential, foundational system-design knowledge — a core component of virtually all scalable systems, working with horizontal scaling to handle load and ensure availability, and necessary understanding for designing systems that scale and stay up.