balancers

How do you change network configuration, load balancers or other external configuration in lock step with your application?

Even during an outage, a request to my domain name will return both the broken and the working load balancers.

There are about 30 nodes representing multiple services, databases, load balancers and processes on the backend.

The point of failure typically comes down to amazon's load balancers or an auto-scaling failure.

A serious setup, however, involves using security groups/private networks and load balancers, also cinder is not supported as a volume backend yet.

Splitting the servers lets you scale them independently; typically, you need just a few frontend load balancers to serve many app servers.

You also need to factor in redundant SAN, hardware load balancers, Master-> Slave mysql databases that do not use your slices resources.

So with 5 load balancers, 1/5 of customers see a one time hit of 30 seconds (after which they return to full speed).

When somebody accidentally drops that table in production or both load balancers go down, I'm your guy.

I suppose an acceptable/respectable use case would be custom load balancers or honey pots.

But when you have dozens of them, you're suddenly managing dozens of load balancers dynamically, and it gets to be pretty chunky to manage at that point.

You use DNS failover and multiple load balancers.

The health checked "multiple load balancers behind a single DNS record" approach has flaws but also simplifies a lot of things.

There is a fair bit of "common" tooling like load balancers and events/log system.

There's not really even a good way to compare the balancers' time-to-balance, since they're both highly configurable (range_ratio and iterations in tempest's case, the 4 balance weights in ES's case) - default values probably aren't "equivalent" in terms of time-to-balance, since it's a very minor concern compared to resource usage and stability.