Today’s definition of multicloud depends on who you ask. This is not a new trend. When a new technological know-how gets some hype, all of a sudden there is semantic confusion. 

My definition is a bit more holistic than most: Multicloud is a assortment of community clouds, non-public clouds, and legacy systems (yes, I went there). Two or more community or non-public clouds ought to be present to be true multicloud. Legacy systems are optional but also very good to include.

A charted representation of my definition appears to be like this: 

multicloud architecture David Linthicum

A little something I’ve discovered more than the decades is that frameworks of any kind have to be generic and relevant to unique dilemma domains. My representation incorporates most of what you will uncover in common multicloud deployments I see today. 

If this seems sophisticated, that’s the position. If the purpose is to get a wholesome multicloud deployment up and working, you will need to have most of these products and services. That list incorporates all the things from price tag governance, storage management, and cloud support brokers, as effectively as orchestration and course of action management—and those abilities require skilled talent.

cio think tank 450x450 IDG

You will need to have a number of more things, dependent on your market, this sort of as compliance management. Figure on at the very least 20 percent to 30 percent more products and services to in the end satisfy your business enterprise wants.

Observe that my multicloud definition incorporates two core meta-layers: 

Information-targeted multicloud deals with all the things that’s stored inside of and outdoors of the community clouds. Cloud-native databases exist in this article, as do legacy databases that even now keep on being on-premises. The thought is to take care of these systems employing common layers, this sort of as management and monitoring, safety, and abstraction. 

Copyright © 2020 IDG Communications, Inc.