> Don't Design for Multiple Cloud Providers
Some industries legally require you to plan for the case where a cloud provider cuts you off. So sometimes you don't have a choice.
Some industries legally require you to plan for the case where a cloud provider cuts you off. So sometimes you don't have a choice.
In those cases, it wasn't "This app needs to be AWS/GCP active/active". It usually meant: if you're building out core functionality to use AWS, you should build out on one of GCP, Azure, etc, too so there's an alternative available. The long term strategy was always to just stick things where they were cheapest to run (on prem, AWS, etc)
(So the same thing came up with physical equipment like Dell and HP servers)
From the business side, there was also concern about Amazon becoming a competitor in the Fintech space but that wasn't regulatory related