Introduction to the strategy of a multi -shame

Companies turn to a more awakening strategy to allow them to select the best cloud service for their specific needs. But finding out how to do such a strategic work, but it is harder and more beneficial than simply hiring a consultant to come and wave multiple pixie dust to your approval infrastructure.

See: What is a multiple architecture? (Techrepublic)

Overview of multiploud strategy

Businesses have been a multi -group from the beginning, but not always intentionally. Like Shadow, it has for decades to use businesses to use unmanageable Mishmash database, operating system and application servers, it also has easy cloud services to include one team Google, while the other uses AWS and other operates Microsoft Azure. This is not a strategy, it’s just a business.

However, businesses are increasingly becoming much more subtle and more clouds’ orders to obtain services with the best breed, lower costs and greater flexibility in moving services more geographically close to users.

See: Kitci Rental: Cloud Engineer (Techrepublic Premium)

Common cases of use for a multi -conventional strategy

By far the most common reason why businesses choose a multi -line strategy are to take Adaiser of specific services available only in the cloud. This is also the best reason to choose access to multiple.

Other boxes using the desire to improve resistance and boundability, but it is often difficult to implement in practical but theoretically argue. Reason? With one cloud you have to take care of the operation of times for this cloud, but with two or more clouds: “Now you have to work and the wicked plumbing between them,” argued Honeycomb co -founder and charity Major CTO.

See: Multicloud vs Hybrid Cloud: Which one is right for your organization? (Techrepublic)

How do you develop a strategy with multiple cross -sections?

The transition to multi -lane architecture is not a decision that should be easily entered because it can represent complexity. Businesses that want to reduce this level of complications can turn to SaaS providers who take care of barden when managing databases or other infrastructure across different clouds. However, it must be remembered that successful deployment depends on architectures that bridge the application and data of the third.

To see how the strategy of multiple deployment was the most successful, it is an IT country to check how Rihat, most sophisticated companies work, as the CTO Miles Ward wrote. What have X (Twitter formals), Snap, Uber and more? Among other things, they moved from monolithic architectures to microservis. This allowed them to optimize the freedom of the developer, although it limited the radius of the explosion when the services failed.

They also made it easier for them to select and choose the best cloud for a particular service. For Snap, the principle of the design of the Cardinal became “facilitated as closely as possible” to make these microprocesses easier with a specific cloud infrastructure.

Several key principles of Snap Design design actually provide a solid base for multicloud strategy of any company:

• Security by default: Verification, authorization and network security should be default, not optional, within the platform.
• Clear department of concerns between the business logic of services and infrastructure. We want a free connection, so each side can iterate independently.
• Abstract differences between cloud providers where we can. We want to minimize the deep dependence of the provider, so it is possible to move services between AWS, GCP and other cloud providers.
• Centralized discovery and service management. We want all service owners to have the same experience for ownership of the service, no matter where the service is running.
• Minimum friction to create new services. The trainee should be able to put the production service for lunch.

From the race, most businesses will miss the resources for building exactly as Snap fees. For ordinary businesses, it may be useful to start with a small one, maybe choose a SaaS provider who processes the complexity of more extension for you, or is simply the beginning by the monolithic application to focus on microservis. One of the advantages of this later approach is that the company puts a good position to push your cloud provider to compete for the right to run individual micro -registers.

When dealing with the strategy, it is also important to consider different aspects of your application infrastructure. Some cloud services are quite standard across the clouds, others are very special for a distinct cloud. And then there are other services that can usually be the same among the clouds, but will require technical work to bridge the gap between.

You will need to determine how much you want a TOPEnd on higher order services in a certain cloud. The more you depend on the service, the more you depend on this cloud. At the same time, the more you can rely on cloud value services, the less your development will have to spend time innovating in this area. There is no correct or bad answer – just a number of multiple selection options.

See: Short Cloud Computing (Techrepublic)

Key metrics of success in strategy with multiple progress

Looking back at the Snap proposal principles, businesses should develop and strictly monitor network performance, security and availability of applications. Businesses should also monitor costs to learn, such as whether Microsoft Azure by Microsoft Azure has been accessible by a micro -service that runs at AWS. In the end, however, the best way to find out if your strategy works is that you are able to operate the best services for your customers.

See: What is a public cloud? (Techrepublic)

Read more

If you want to explore this topic more, there are cloud articles in Techrepublic.

Techrepublic Premium also offers cloud recruitment sets, principles and control lists to improve IT and HR work.

Publication: I work for Mongodb, but opinions here are mine.

This article was originally published in August 2022. Antony Peyton was updated in July 2025.