Interview Bootcamp
Vote

0% completed

​

High Availability and Fault Tolerance

Redundancy and failover strategies for load balancers

To ensure high availability and fault tolerance, load balancers should be designed and deployed with redundancy in mind. This means having multiple instances of load balancers that can take over if one fails. Redundancy can be achieved through several failover strategies:

  • Active-passive configuration: In this setup, one load balancer (the active instance) handles all incoming traffic while the other (the passive instance) remains on standby

.....

.....

.....

Like the course? Get enrolled and start learning!
C

camelBack

· 3 years ago

Did I read it right that if you have multiple LB's due to the active-active setup, you need an LB to distribute traffic to them?

If that's correct, doesn't it move the bottleneck / single-point-of-failure to that new LB? (chicken-egg scenario)

C

curie

· 3 years ago

How does active-active redundancy method provide better resource utilisation than active-passive, as in the latter, the passive resources are only used once active instance fails?

Show 1 reply
k wargs

k wargs

· 2 years ago

Beyond simplicity, would an active-passive failover strategy have the benefit of ensuring consistent performance? If the primary load balancer fails, its replica is designed to handle the same load so there would be no noticeable impact to the performance of the system. If a load balancer fails in an active-active configuration the total amount of load balancing resources has decreased which could potentially affect the throughput.

Show 1 reply
Y

yong.9900

· 7 months ago

In my mind, state is a configuration which is changed and used frequently, I feel it should be treated only as centralized config management. data sharing (redis and memcached are consistant at best, they are not reliable, thus should not be used in this case?