3 ms·
> 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'
by frenchman99 5y ago
> 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.
- albert_e 5y agoWhat are some actual examples of industries (which geography) that have multi cloud a sa requirement?
- nijave 5y agoI'm not sure on the legal particulars, but it was mentioned when I worked at JP Morgan Chase. I think most of it revolved around vendor management and vendor relations. It wasn't just AWS--for such a big business, a single provider anywhere represented a lot of risk 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