Multicloud must be straightforward, proper? I imply, it’s simply deploying and managing greater than a single public cloud. This has sadly not been the case. As extra enterprises deploy multicloud architectures, some avoidable errors are occurring over and over. With a little bit of understanding, maybe you possibly can keep away from them. Let’s assessment the highest two:
Not designing and constructing your multicloud with cloudops in thoughts. Many enterprises are deploying two, three, or generally extra public clouds with out a clear understanding of how this multicloud structure can be managed long run.
When a multicloud deployment strikes to manufacturing, there’s a large number of cloud companies attributable to leveraging a number of public clouds with redundant companies (equivalent to storage and compute). It all turns into an excessive amount of for the cloudops workforce to take care of. They can’t function all of those heterogenous cloud companies in addition to they need to, and the standard of service suffers. It additionally locations means an excessive amount of danger on the deployment when it comes to safety and governance operations.
There are a couple of methods to keep away from this. First, don’t do multicloud if you happen to’re not prepared to step as much as the operational wants. Stick with single cloud deployments solely. This takes all best-of-breed companies off the desk and reduces the worth in utilizing cloud in any respect. The second, and the right strategy, is to automate just about the whole lot and to leverage abstractions (single pane of glass) to handle the complexity and nonetheless present best-of-breed advantages.
Choosing “cloud native” the whole lot. Keep in thoughts that instruments that span the general public clouds are essentially the most helpful. You can use the identical interfaces and automation from one cloud to a different in your multicloud.
This looks like the plain selection, however many enterprises shifting from single to multiclouds are maintaining the native instruments that got here with a specific public cloud, equivalent to safety and operations instruments. Companies that choose to maintain particular administration and monitoring instruments for AWS, Microsoft, or Google must study and leverage a instrument per public cloud. Not very environment friendly.
Avoiding this downside is straightforward to know, however not really easy to drag off. Although cloud-native purposes are positive, solely utilizing native instruments for all kinds of administration and safety duties is simply not a good suggestion. You’ll want individuals who perceive every instrument, there gained’t be intercloud communications and coordination, and automation must happen in a number of locations…
