Even if we were concerned about our current vendor lock-in or displeased with our current vendor, maintaining our site on a single cloud already eats up more devops overhead than our team of three and a half server-side engineers can really afford. And doubling our monthly hosting costs in the name of redundancy (we do already have some redundancy within our existing cloud) isn't a good investment given our business model.
Yes, we had downtime when S3 died last year. So did half the Internet. Our customers understood and our business was impacted more by being unable to use Slack for a few hours than by our site going down for that time.
And if we became dissatisfied with our vendor, we would just make it a project and switch clouds. It would take a month or two, but so would setting up a multi-cloud setup. And once we switched we would be done. No ongoing additional overhead.
And if you think there's any sort of API or unifying panel that would eliminate the additional work of maintaining multiple clouds, I've got this really lovely bridge to sell you....
If we had a business and team the size of, I don't know, Uber, or equivalent availability requirements ... sure, it might be worthwhile. But for a small or medium sized startup, the problems that multi-cloud could solve are the wrong problems to be worrying about.
