Doing so is phenomenally expensive.
It’s demonstrably little more expensive than running more instances on the same provider. I only say -little- because there is a marginal administrative overhead.
Doing so is phenomenally expensive.
It’s demonstrably little more expensive than running more instances on the same provider. I only say -little- because there is a marginal administrative overhead.
If you properly divide your instances between providers and regions and use load balancing which uses a corum of 3 availability model then it can be zero downtime pretty fairly guaranteed.
People be cheap and easy tho, so 🤷♂️
Crowdstrike No!


You do lighting for Linkin Park, and you got a sweet packet with Linkin Park written on it in front of you, and are posting an image of same with Linkin Park in the middle of the image. You still misspell the name.
TLDR: about 3-ish.
Quick, someone report a bug!
The dog (who is called Muffin) is saying “Let me merge”


Penny counters who don’t like paying for storage
In my experience using containers has removed requirements for additional engineering cost to deploy between providers because a container is the same wherever it’s running, and all the providers will offer container hosting, and most offer cluster private networking.
Deployment is simplified using something like octopus which can deploy to many destinations in a blue-green fashion with easy rollback.