
Lie 1. Multicloud means freedom from tyranny. I understand what this premise means. Using multiple cloud provider services avoids dependence on a single cloud provider. It is plausible. However, this is not necessarily the case.
The reason is simple. This is because using the native API of a specific cloud provider is a dependency. Currently, services such as security, storage, governance, and even pinops APIs used by one vendor cannot be ported to another vendor’s service. Even if you could, you should work with another cloud-native service provider to fix the code. This is a situation that corresponds to the definition of subordination that we already know. Ultimately, it doesn’t matter how many different cloud providers you use. The native API problem remains.
Lie 2. Multicloud is more profitable. This part is a little self-explanatory, but first of all, multiclouds are likely to cost more than single clouds, and it’s understandable why. Indeed, security and cloud operations are becoming increasingly complex and more diverse technical experts must be hired to effectively operate multiple clouds. As such, multiclouds are more expensive and riskier. As the number of components that can be ported between clouds increases, the complexity of adding architectures also increases.
Many companies are embracing multicloud, driven by flexibility and the ability to innovate with the best cloud services. This is why multicloud is built, introduced and operated at a higher cost. Ultimately, however, you’ll have to decide if this new technology is right for solving the problems your business is facing. Only when this premise is met is it worth the extra cost.
Lie 3. Multicloud should not extend to traditional systems. Not like this. This is my personal opinion, but as with any multicloud issue, it may vary.
Rather, I believe that all systems (legacy, edge, SaaS, and even small industry-specific clouds) should be considered from the outset as part of a multicloud infrastructure. This allows all systems to be managed from a common control unit. It is a concept commonly referred to as supercloud or metacloud. However, this means that you must resolve all issues related to the security and operation of all systems, data management and application deployment, not just services from a few large public cloud providers.
It is certainly not an easy road. However, in this way, most systems can be grouped under the same management and security framework. It also eliminates the need to diverge from native tools that use siled technologies. Multicloud infrastructure can become more complex and expensive, but solving this problem in an integrated and scalable way extends what works in multicloud to other platforms.
So far, we’ve looked at three of the most glaring misconceptions about multicloud. Of course, depending on the company, there may be a clear reason why the system is not included in the multicloud framework, and if so, there is no problem. However, these misunderstandings need to be made more public. It should not be easily overlooked.
editor@itworld.co.kr


