Are you ready for multicloud? A checklist

Perhaps you deployed your first cloud-native Node.js application to Amazon Web Services and then received a new assignment to port over several legacy .NET applications to a public cloud. Should you try Amazon Lightsail as a first step, or should you review Microsoft Azure’s options for .NET developers?

Or maybe your team has applications running on Azure that need to securely connect to machine learning models deployed by the data science team on Google Cloud Platform. It’s easy to conceive scenarios where development and data science teams end up exploring, prototyping, and deploying applications, databases, microservices, and machine learning models to multiple public clouds.

For larger enterprises, supporting multiple clouds is almost inevitable, due to the herculean level of governance required to channel all development, data science, and shadow IT efforts to a single public cloud. Even so, there are several reasons why global businesses and larger enterprises determine that “being multicloud” is strategically important.

I reached out to several experienced IT leaders active on Twitter through social chats like IDGTechTalk and CIOChat to get their perspectives on whether and how organizations should support multiple clouds. I’ve included their opinions and insights in this checklist on multicloud readiness. Are you ready?

Ease into multicloud complexities 

IT leaders know the complexities of setting up secure and robust cloud infrastructures. Naturally, these complexities multiply when you combine multiple clouds. You should strive to avoid dealing with them all at once. 

Operating across multiple clouds is complex because of the required governance, technical expertise, and integrations. As Sarbjeet Johal, an independent technology strategist, puts it, “Nobody gets up in the morning and says we are going to do multicloud today. They just fall into it, mainly due to organizational silos. Multicloud is as easy as 1-2-3… said no one ever!”

Copyright © 2020 IDG Communications, Inc.

Source link