Load balancing is something most of us assume is a solved problem. But the idea that load balancing is "solved" could not be further from the truth.
If you use multiple load balancers, the problem is even worse.
Most of us use "random" or "<a href="https://en.wikipedia.org/wiki/Round-robin_scheduling">round-robin</a>" techniques, which have certain advantages but are highly inefficient.
Others use more complex algorithms like "least-conns", which can be more efficient but have horrific edge cases.
"Consistent hashing" is a very useful technique, but only applies to certain problems.
There are several factors that exist both in theory and practice that make efficient load balancing an exceptionally hard problem.
<p>
For instance:
<ul>
   <li>Poisson request arrival times</li>
   <li>Exponentially distributed response latency</li>
   <li>Oscillations when sharing data between multiple load balancers</li>
</ul>
Luckily, there are techniques and algorithms that have been developed that can make life better.
I'll walk through some of the ways that we can do better than "random", "round-robin", and naive "least-conns", even with distributed load balancers.