3 surefire ways to kill your multi-cloud deployment

You can do more wrong than right when it comes to multi-cloud. These three tips will keep your implementation in good health.

Flexera’s report confirms that multi-cloud deployments are increasingly becoming a two-cloud race between public cloud providers. Of all respondents, 50% of businesses have significant workloads on AWS and 41% run those significant workloads on Azure. Google Cloud has a 22% stake. What they have in common is explosive growth in 2020 and, I’m sure, continued growth this year.

Honestly, I don’t care who is winning the race to become the top public cloud provider. It’s more about how you leverage these clouds in ways that allow you to solve business problems.

The reason to move to multi-cloud is not so much to avoid locking, but to have the choice to build applications and migrate to the cloud. Most businesses use two or more public cloud brands, that is, multi-cloud. But you can kill a good multi-cloud deployment unless you consider these three recommendations.

Choose popular, cloud-based tools. The worst thing you can do when building a multi-cloud solution is the silo tools and technologies in each cloud. This includes security, administration, performance tools, and more.

Drive agile to the cloud: Checklist for multi-cloud success

The end result is a tool for every public cloud. When all are handed over to cloudops groups, they have to deal with at least nine tools, which require different skills and training. Complexity often means that multi-cloud implementations end up not working practically. You need to find popular tools that work in the cloud.

Understand the cost of adding the cloud. If you are supporting two public clouds, the cost of adding one more cloud should be the same, right? Wrong. It really depends on what you’re doing with that particular public cloud.

If you have 100 apps and databases connected on one cloud and 150 on another, if you add a public cloud of only 5, the operating cost per app increases for that public cloud provider. So those who want to add a new public cloud to our multi-cloud need to demonstrate solid, cost-effective reasons. Remember that the cost of running per cloud provider is mostly fixed.

Avoid a culture of unobstructed choices. Multi-cloud means choice – choice in security services, application development tools, databases, etc. However, choosing different net new cloud services increases complexity and complexity increases risk and cost.

This is a trade-off. We want developers and other innovators to choose whatever service is the best they want to use. However, if they move to new services, you will likely have redundant services to work on in the back, such as multi-security services, multi-database services, and so on.

Be the first to comment

Leave a Reply

Your email address will not be published.