Load balancing, explained without the jargon

It comes up on almost every project, usually later than it should. Here is load balancing without the vocabulary that usually surrounds it.

Operability is a feature, and it has to be built rather than bought. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

The short version

Health checks decide whether load balancing helps or hurts. The teams that handle this well are rarely the ones with the biggest budgets. Doing this properly once is usually cheaper than doing it approximately three times.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The cost of getting this wrong is rarely visible on the day it happens.

Sticky sessions quietly limit how far you can scale. None of that requires a large budget, only a decision and someone to own it. It is the sort of thing that looks like polish right up until it costs you an enquiry.

Turning this into a decision

Test what happens when one instance is slow rather than dead. This is the sort of thing that compounds, quietly, in both directions. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

In practice

Cloud work rewards teams who automate early and punishes teams who click through consoles. Three things worth confirming about load balancing before you move on:

• Someone can say what the current setup is without going to look
• Health checks decide whether load balancing helps or hurts — and you know whether that is true here
• There is a way to tell whether the last change to this helped

The point is not perfection, it is knowing which of these you have consciously chosen to skip.