Why load balancer?

Same fleet, same traffic. Pin every request to one server, then spread it across the fleet — including a mid-run outage.

1
Part 1 · Watch the concept

The idea in 24 seconds

A fixed animation — no controls, nothing to configure. It shows the shape of the problem and the shape of the fix, with the story written out underneath.

Loading player…

~24s animated walkthrough: traffic pinned to one server vs. spread across a load-balanced fleet.

The story the animation tells

Three app servers, and the client knows all three by address: 10.0.1.5, .6, .7. Those IPs are compiled into the app, which is fine — until anything about the fleet changes. Watch the badges on the client box; that list is the whole problem.

Traffic grows, so ops does the right thing and starts a fourth instance. It boots, it's healthy, it's ready to work — and it sits there taking nothing, because no client has ever heard of 10.0.1.8. Capacity you're paying for that cannot be reached.

Then the opposite happens: one instance dies. The clients don't find out. They keep sending requests to an address with nothing behind it, and every one of those users sees an error — not because the system is out of capacity, but because a third of the traffic is aimed at a corpse. You can't fix either problem from the server side. The routing decision lives in code you already shipped.

So a load balancer takes the IP list's place. The client now knows exactly one address and stops caring how many servers exist. Health checks mean a dead instance is pulled out of rotation in seconds and traffic reroutes to the survivors. Service discovery means the fourth instance registers itself and starts receiving work the moment it's healthy. Round robin spreads the load instead of pinning it. Nothing on the client ever changes again.

The point. A load balancer is less about splitting load evenly and more about who gets to decide where a request goes. Move that decision out of the client and behind one address, and scaling up, losing a node, and deploying all become routine instead of a client release — at the price of a component that now sees every single request.

2
Part 2 · Run the numbers

Interactive traffic simulator

Now drive it yourself. Pick a mode and an algorithm, set the traffic rate and capacities, kill a server mid-run, and watch real counters — per-server queues, drops, requests served — respond to your settings.

Single fixed address
All traffic is pinned to Server 1. The other servers sit idle no matter how loaded Server 1 gets.
sent
0
success
—
errors
0
idle servers
3
Server 1 (pinned)
healthy
queue 0.0 · served 0
Server 2
healthy
queue 0.0 · served 0
Server 3
healthy
queue 0.0 · served 0
Server 4
healthy
queue 0.0 · served 0
Last routing decisionst = 0.0s
Run traffic to see routing decisions.
Why this matters
  • Capacity you paid for goes unused. Without a load balancer, everything funnels through one server while the rest of the fleet idles.
  • One dead server means an outage, not a dip. Kill Server 1 in "No load balancer" mode and every request fails — the client has no other address to try. Kill any server in "Load balancer" mode and traffic just reroutes.
  • The algorithm matters under skew. Round robin assumes uniform requests; least-connections adapts when some requests are heavier than others.
Traffic console
Run traffic, then take a server down mid-flight.
Try this
Run traffic until Server 1 turns red, then click its power icon. Every new request fails immediately — there's no fallback address.