4 ms·
Thanks for the detailed reply! It's been fun engaging with you. You have really hit the nail on the head about risk, and what it means to go "all-in" on a part
by dolni 5y ago
Thanks for the detailed reply! It's been fun engaging with you.
You have really hit the nail on the head about risk, and what it means to go "all-in" on a particular provider.
There's a very relevant case to be made for electing to remain provider agnostic if your business is sensitive to outages. There is a balance between avoiding administrative overhead and mitigating risk.
I like to think about it like buying insurance (I'd put security posture in the same bucket, too). Pursuing a cloud-agnostic design has some cost per month. A cloud vendor outage has some chance of happening per month, and if it does occur it will cost you $X. The business needs to figure out when:
cost(cloud-agnostic design) < risk(cloud vendor outage) * cost(cloud vendor outage)
Figuring that out isn't trivial, especially because a large part of cost(cloud-agnostic design) will be in employee hours. At best you probably get a ballpark estimate.