Most think of multicloud just how it sounds: an architecture that leverages plural public and/or private clouds at the same time, in support of best-of-breed cloud services. In other words, we use multicloud as a path to access the cloud services that are the best fit.
As multicloud becomes the norm , I’ve observed that the design and deployment of multicloud-based architectures is really not about the underlying clouds. There are a few reasons for this:
[ Learn all about the cloud at InfoWorld. Start with the basics: What is cloud computing? Everything you need to know now . Then learn what is IaaS (infrastructure as a service) , what is PaaS (platform as a service) , and what is SaaS (software as a service) . | Get ready for the latest trend in cloud computing: What is multicloud? The next step in cloud computing . ] First, technology to manage multiclouds should sit above and separate from the cloud-native resources it is managing. It does not matter if the tools are for AIops, identity and access management, network monitoring, metadata management, etc. When deploying multiclouds, it’s always better to leverage technology that spans the clouds and is not limited to operating a single branded platform.
To read this article in full, please click here