Mastering Load Balancing: Types, Tools, and Algorithms Explained

What is Load Balancing

In the early stage of a website, a single machine provides centralized service, but as traffic grows, performance and stability become challenges; scaling out with a cluster requires a way to distribute user requests to multiple machines, which is the role of load balancing.

Most internet systems use server clusters (web, database, cache, etc.). A load balancer sits in front of the cluster, receives client requests, and forwards them to appropriate backend servers, making the forwarding transparent to the client.

Load Balancing Types

Load balancing can be classified mainly into Layer 2, Layer 3, Layer 4, and Layer 7 approaches.

Layer 2 Load Balancing

The balancer presents a virtual IP (VIP) while backend machines share the same IP but have different MAC addresses; the balancer rewrites the destination MAC address to forward traffic.

Layer 3 Load Balancing

Similar to Layer 2, but backend machines have different IP addresses; the balancer forwards based on IP after applying a scheduling algorithm.

Layer 4 Load Balancing

Operates at the transport layer (TCP/UDP); the balancer modifies IP and port information to forward traffic to application servers.

Layer 7 Load Balancing

Operates at the application layer, using protocols such as HTTP, DNS, etc., to make routing decisions based on URL, browser type, language, and other request attributes.

Common Load Balancing Tools

Software solutions dominate the industry due to cost; popular tools include LVS, Nginx, and HAProxy.

LVS (Linux Virtual Server)

LVS provides high‑performance, high‑availability server clusters at Layer 4. Its architecture consists of a front‑end load balancer (Director), a server array of real servers, and optional shared storage.

Nginx

Nginx can act as a reverse proxy and Layer 7 load balancer, supporting up to 50 k concurrent connections officially, with many extensions for modular design, high reliability, low memory usage, hot deployment, and rich load‑balancing strategies.

Modular design: easy to extend via modules.

High reliability: master and worker processes synchronize; a failing worker is instantly replaced.

Low memory consumption: ten thousand keep‑alive connections use only ~2.5 MB.

Hot deployment: configuration changes reload without stopping the server.

Strong concurrency: official claim of 50 k requests per second.

Rich features: powerful reverse‑proxy and flexible load‑balancing policies.

HAProxy

HAProxy is an open‑source solution offering high availability and both TCP and HTTP load balancing, commonly used for high‑traffic web sites.

Typical Load Balancing Algorithms

Static algorithms: Round Robin, Weighted (Ratio), Priority.

Dynamic algorithms: Least Connections, Fastest, Observed, Predictive, Dynamic Ratio, Dynamic Server Addition, QoS, ToS, Rule‑based, Consistent Hashing, Modulo‑based, etc.

Each algorithm has its advantages and suitable scenarios, such as read‑only databases, cache systems, or mixed read/write workloads.