What is load balancer? Plain-English meaning

Short definition: A load balancer is a system that distributes incoming network traffic across multiple servers so no single server becomes overwhelmed.

Plain-English explanation

When a website gets many visitors at once, one server might struggle to respond quickly. A load balancer sits between users and the servers, deciding which server should handle each request. It uses methods like round-robin or least connections to spread the load fairly. This helps keep response times low and reduces the chance of a server crashing. Load balancers also check server health and can redirect traffic if one server fails.

Why it matters

You care about load balancers when you run a website that expects many visitors or when you notice a site slowing down during peak hours. Without load balancing, a popular site could become slow or unavailable. Understanding load balancers helps you see why big sites rarely go down and how they maintain speed.

Concrete example

Imagine an online store expecting a big sale. The store uses three servers to handle product pages and checkout. A load balancer receives every customer request and sends each one to the server with the fewest current tasks. If one server crashes, the load balancer stops sending it traffic and the other two continue serving customers.

Common confusion

A load balancer is sometimes confused with a reverse proxy. A reverse proxy forwards requests to a single backend server and can also cache content, while a load balancer distributes traffic among multiple servers. They can be combined, but they serve different purposes.

Related terms

server, CDN, caching

How people actually use it

System administrators deploy load balancers in front of server clusters to route requests based on algorithms like round-robin or least connections. They are used in cloud environments, data centers, and web applications to manage traffic spikes and maintain uptime.

Related terms explained

reverse proxy

A reverse proxy is a server that sits in front of backend servers and forwards client requests to them. It can provide caching, load balancing, and security features such as hiding the backend architecture.

Example: A website uses a reverse proxy to cache static content and distribute requests to multiple application servers.

round-robin

Round-robin is a simple load-balancing algorithm that distributes requests sequentially across a list of servers in a circular order. It is easy to implement and works well when servers have similar capacities.

Example: A load balancer sends the first request to server A, the second to server B, the third to server C, then repeats.

health check

A health check is a test performed by a load balancer to determine if a backend server is available and able to accept traffic. It typically involves sending a request and expecting a specific response, and servers failing the check are temporarily removed from the pool.

Example: A load balancer pings each server every 30 seconds and stops sending traffic to any that do not respond.

horizontal scaling

Horizontal scaling, also known as scaling out, involves adding more servers to a system to handle increased load. Load balancers are essential for distributing traffic across these additional servers.

Example: An e-commerce site adds several new virtual machines during a sale, and a load balancer distributes traffic among them.

Practical tips

Array

Common questions

Array

Key takeaways

Array

Step by step

Array

More context

Load balancers can operate at different layers of the network stack: Layer 4 (transport) load balancers route based on IP and port, while Layer 7 (application) load balancers can make decisions based on content like URLs or cookies. In cloud environments, load balancers are often managed services, automatically scaling and providing high availability. They are a key component of horizontal scaling strategies.

Additional background

Array