IDG Blog | 3 must-haves in a multicloud architecture

Most cloud architects find that their world suddenly becomes a heterogeneous environment. At one time, we could only focus on one public cloud service provider, but now there are at least three or four public clouds in the mix. Accordingly, the architectural pattern has changed from Intra Cloud to Inter Cloud, which is where complexity and risk lie.
ⓒ Getty Images Bank

As a result, if you’re an architect, you’re in the process of making sure that everyone, including me, can cover most of the underlying services. It’s as if the pilot was using a pre-flight checklist. This includes cross-cloud governance, security, operations, and more. However, we often omit some essentials for a successful multicloud, and here are the three most important.

Centralized cross-cloud user account management. To properly implement multicloud, a group of public cloud service providers should be treated as one cloud as possible. There should be a common user management layer so that user layers can be added, deleted, and changed from a single point of control that interacts so-called’native’ with each cloud.

In addition to making user management less cumbersome, centralized account management also improves security by making the identity displayed to each cloud service provider consistent. The IDAM system is also more consistent, and cloud security is thus more secure.

Cross cloud resource management. This category could be anything that monitors resource usage such as storage, compute, or provisioning, such as AIOps tools and cloud management platform tools. Of particular importance is the automated deprovisioning of unused resources being brought back to the resource pool. It can prevent public cloud service providers from charging for these resources.

I’ve gotten a call from someone who panic after allocating a huge amount of cloud resources and not stopping. The charges are huge, but it’s not easy to ask a cloud service provider to understand this mistake. In a multi-cloud environment, the likelihood of these expensive mistakes increases, so you need to pay more attention.

Generalization of assets. Suppose that a database of the same brand is used for each cloud within a multi-cloud environment. It is not very efficient in terms of cost and operation. Licensing costs are likely to be higher than necessary, and they will be cheaper to run the same resources in one cloud.

IT departments often think of using the same database in more than one cloud as redundancy. It means that valuable data eggs are not placed in a basket called a public cloud. If one cloud service provider fails, the same database can be moved to another cloud.

Of course, there may be risk-reducing effects, but running a production database using the same technology and brand on more than one public cloud service provider might not be the best approach. There are ways to reduce risk, but are less complex and less expensive. Once again, check out the checklist to define a better way to solve business problems of the same nature.

Building a multi-cloud is not easy. Of course, in the next few years, you will get better from what you learn from the mistakes of many companies, but now you have to try not to be the same company that made the mistakes. [email protected]

Source: ITWorld Korea by

*The article has been translated based on the content of ITWorld Korea by If there is any problem regarding the content, copyright, please leave a report below the article. We will try to process as quickly as possible to protect the rights of the author. Thank you very much!

*We just want readers to access information more quickly and easily with other multilingual content, instead of information only available in a certain language.

*We always respect the copyright of the content of the author and always include the original link of the source article.If the author disagrees, just leave the report below the article, the article will be edited or deleted at the request of the author. Thanks very much! Best regards!