So Cloud Hopping is an idea that you can dynamically relocate your infrastructure on the fly an utilize software like https://libcloud.readthedocs.io/en/stable/compute/pricing.html to make those choices. Relying on a particular vendors flavor of database can be dangerous. I am old and grumpy so when I say the what-ifs need to be in the README of any architecture, I share it out of memory and pain. </rant> Now I expect spam emails from this reply. :( On Tue, Oct 21, 2025 at 11:14 AM Shaun Potts via Outages-discussion <outages-discussion@outages.org> wrote:
this guy gets it
multi cloud isn't i need to deploy my 8 servers in 2 locations, it's i need to deploy 4 servers in 2 locations and make my software be able to use either if the other is unavailable
it's not rocket science but c levels sure make it seem like it is
On Tue, Oct 21, 2025, 12:47 PM Peter Beckman via Outages-discussion < outages-discussion@outages.org> wrote:
On Tue, 21 Oct 2025, Jeff Shultz via Outages-discussion wrote:
Truly fault tolerant is not budget friendly.
Having worked for AWS, and having run multi-region fault-tolerant systems for many years, it *can* be budget-friendly, if you are willing to put in the effort and planning.
I can find two different hosting companies that offer bare-metal hosting, and confirm that both are using a different mix of connectivity on different ASNs, and are in geographically different areas.
I can deploy my workload across those systems, reducing risk, but also have the workload spread across those disparate systems, so I don't need to double my infrastructure costs.
This is even possible in AWS -- they provide multiple tools for multi-region and multi-AZ deployments. When I worked for AWS my team built AMI Copy in 2012/2013, so you could move AMIs between regions with an API call, making it easier to start up new EC2 instances with your existing images.
RDS has cross-region read-replicas. DynamoDB was built with multi-region in mind.
You DO need to assume and plan that a whole AZ or Region will go dark, and if your systems just immediately fail when that happens, then you've done a less-than-ideal job of building your systems to be fault-tolerant.
Yes, it adds complexity and you have to test regularly, but it does NOT need to add huge amounts of additional costs. You just need to know what you're doing.
Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com https://www.angryox.com/ --------------------------------------------------------------------------- ______________________________________________ Outages-discussion mailing list outages-discussion@outages.org Sign up for an account https://lists.outages.org/accounts/signup/ To subscribe send an email to outages-discussion-join@outages.org To unsubscribe send an email to outages-discussion-leave@outages.org To contact the list owners outages-owner@outages.org Archives https://lists.outages.org/archives/list/outages-discussion@outages.org/
Thank you for using outages-discussion Lists!
______________________________________________ Outages-discussion mailing list outages-discussion@outages.org Sign up for an account https://lists.outages.org/accounts/signup/ To subscribe send an email to outages-discussion-join@outages.org To unsubscribe send an email to outages-discussion-leave@outages.org To contact the list owners outages-owner@outages.org Archives https://lists.outages.org/archives/list/outages-discussion@outages.org/
Thank you for using outages-discussion Lists!
-- - Andrew "lathama" Latham -