I study the design of scalability, and I hardly think about ways to ensure that the load balancer does not become a single point of failure. If the load balancer drops, who decides to switch to the backup balancer? What if this “decision maker” drops too?
The point to avoid load balancing as the only point of failure is that the load balancer runs in a high availability cluster with hardware backup.
I believe that the answer to this question is redundancy .
, , ///-, // .
, ., - , .
, , , , , .
, , , . : " , ?", , p, , n ( ), p^n. , , , .
p
n
p^n