Why’s that? Massive multi-zone, multi-region outage with no comms for >30 minutes, and the rise of K8S seems like the perfect time to get serious about multi-cloud.
-
That’s just another way of saying it’s a business decision - if you really don’t need 4 9’s, you shouldn’t design for it, it will be way more expensive. But, if you’re Snap and every minute down is millions of dollars, you have a compelling business case for multi-cloud.
Not if it costs (more) millions of dollars and distraction/opportunity cost to be multi-cloud. Outages are acceptable tradeoff.
-
-
Like all architecture, it depends. Designing your application for high portability, and using a PaaS that enables that is a defensible decision, regardless if you’re ok with outage. And, some use cases have very low outage tolerance (medical devices, for instance)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.