[999900000999]

The idea would be to actually load distribute between different cloud providers.

But even then , the load balancer needs to run somewhere. Which becomes a new single point of failure.

I’m sure someone smarter than me has figured this out.

[jethro_tell]

yes, they have. It just costs a shit ton of money and is extremely difficult to get the suits to sign off on TWO full 'cloud services' bills. It generally doubles your cost and workload and increases your uptime by a couple hours/year, assuming you don't have bugs that affect one or the other cloud in your deployment stack.

It's basically a wash for almost all organizations for twice the cost and effort.

[999900000999]

Ok...

But where does the load balancer actually run. Does load balancer main run on AWS, and load balancer backup on Oracle?

[dboreham]

Short TTL DNS or BGP anycast.

[grogenaut]

also these things don't go down THAT often... well aws, not some others. More uptime that you probably had before. even the stock market takes a few days off every decade. Just ask W.

[justinclift]

> not some others.

Looking at Azure and GitHub in particular. ;)

[JackSlateur]

DNS

[erikerikson]

Not really. Your clients can random robin to connection points across providers and move write heads upon connection. If you worry about hard coding you can reduce the surface to a per-context first minimum contact point.