While multicloud is a big hit these days, it's important to remember that most clouds are complex and distributed architectures.
Multicloud should be easy. It's just deploying and managing one or more public clouds, but unfortunately it's not easy. As more and more enterprises implement multicloud architectures, avoidable mistakes continue to occur. With a little understanding, you can avoid it. Among these, we will look at two representative.
When designing and building a multicloud, don't keep Cloudops in mind. Many companies are implementing two, three or more public clouds without a clear understanding of how to manage this multicloud architecture over the long term.
When a multicloud deployment moves to an operating environment, a large number of cloud services occur using multiple public clouds along with redundant services such as storage and computing. The CloudOps team is too overwhelming to handle this. Service quality deteriorates because all these heterogeneous cloud services cannot be properly operated. It also poses too many risks to deployment in terms of security and governance operations.
There are several ways to avoid this. First, you shouldn't run multicloud unless you are willing to meet operational requirements. Focus on a single cloud deployment. This prevents all of the best-in-class services from being utilized, and significantly reduces the value of using the cloud. A good approach would be to automate almost anything, use abstraction (single window, SPoG) to manage complexity and still provide best-of-breed benefits.
Select everything as'cloud native'. Keep in mind that tools that cover the public cloud are the most useful. In multicloud, the same interface and automation can be used between clouds.
This may seem like a natural choice, but many companies migrating from single cloud to multicloud retain the native tools that come with certain public clouds, such as security and operations tools. Companies that choose to maintain specific management and monitoring tools from AWS, Microsoft, or Google will need to learn and utilize the tools on a per public cloud basis. Not very efficient.
Avoiding this problem is easy to understand, but not easy to solve. Cloud-native applications are great, but using only native tools for all sorts of management and security tasks is not a good idea. It requires someone who understands each tool, there is no need for communication and coordination between the clouds, and automation needs to be done in multiple places, not just one. The solution is to find a tool that provides a consistent interface across the cloud.
Multicloud is still evolving. Public cloud providers don't provide good guidance and tools because it's not in their best interest to convert their business customers to a multicloud environment. However, if cloud vendors lead to a path that increases complexity, cost, and risk, that path should be avoided.
0 Comments