A load balancer sits between clients and a pool of identical servers, sending each request to whichever one looks least busy. It is also where TLS often terminates and where unhealthy hosts quietly disappear.
In plain language
In infrastructure and DevOps, this is part of the toolkit that keeps services running across many machines. A load balancer sits between clients and a pool of identical servers, sending each request to whichever one looks least busy. It is also where TLS often terminates and where unhealthy hosts quietly disappear. If you are new to the field, the simplest mental model is this: a traffic cop that spreads requests across servers. Read it once with that frame in mind, then come back and read it again — that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of Load Balancer as the wiring inside a wall. Nothing about it is interesting until the lights go off — at which point it is the only thing anyone wants to talk about.
Where it shows up
Load Balancer quietly carries the weight of running software in production — deploys, scaling, traffic, incident response. Users rarely hear about it, which is exactly the point.
A small example
Imagine the scene above. The role Load Balancer plays is the one its blurb describes — A traffic cop that spreads requests across servers. When a website stays up through a sudden traffic spike, ideas like this are part of the quiet machinery that absorbed the load.
Common misunderstanding
One line to take with you
Load Balancer is most successful when nobody is talking about it. Build it so the room stays quiet.