I was going to say something similar. I get that this was a very basic explanation of what load balancing can be but very rarely have I seen it implemented in

I was going to say something similar. I get that this was a very basic explanation of what load balancing can be but very rarely have I seen it implemented in such a fashion, as described - that is, 'serving toast, when finished with the toast, that toaster gets more toast, etc.' There are so many types of load balancing, and so many different ways to guard, simply with best practices, against what this story explains. I also found the 'quadruple hump' in a graph reference difficult to follow without more of a backstory of what the graph was representing. I also don't understand why it would be so difficult to grep through the logs of that load balancer (or load balancers) and find that common fault on the backend.