fbpx
Blog September 12, 2019

Why Multi-Cloud Strategy Beats Single Cloud Almost Every Time

Our economy is an increasingly digital one, which not only means more pressure on infrastructure but also higher user demands when it comes to things like uptime and response latency.

Enterprise organizations, for their part, are looking to run their workloads within the most appropriate environments, both to take advantage of cost savings and to leverage the capabilities of distinct platforms. Every cloud provider has relative strengths and drawbacks, and smart cloud teams are learning how to use these in combination—sometimes using multiple providers to complete a single user transaction. Microservices-based architecture is making this even more common. If that multi-cloud architecture is well managed, every transaction (or part of a transaction) can be shifted as needed. Check out why we feel that a multi-cloud strategy is appropriate for most enterprise organizations below.

Review: What is a Multi-Cloud Strategy?

Multi-cloud refers to the use of multiple cloud computing services, in a single heterogeneous architecture, at the same time. These can be public clouds (like Amazon AWS, Microsoft Azure, or Google GCP), or a mix of public and private clouds.

Simply using different clouds in different departments falls well short of an actual strategy for using multiple clouds, however. So is simply deploying workloads across different cloud environments. Although having different public clouds in different departments might be what started organizations on their “multi-cloud journey,” many are now pivoting to an approach that bakes multi-cloud into their infrastructure and software plans right from the start, using modern multi-cloud management tools.

Being intentional and proactive about using multiple clouds, and finding the right tools to manage them, is the core of a true multi-cloud strategy.

Single Cloud vs. Multi-Cloud Strategy

When cloud computing first came on the scene, it really did seem that one cloud solution could meet all of an organization’s needs. They started simply by moving applications to public cloud infrastructure, maybe with some refactoring involved. Once the concept proved solid for less mission-critical applications, organizations started moving more and more to—or simply building in—the cloud they had chosen.

Multi-cloud environments arose for many different reasons:

  • Different departments or branches within the same organization procured cloud services independently of each other.
  • IT departments, wanting to ensure better disaster recovery (DR) and avoid vendor lock-in, began mirroring their public cloud deployments on another platform.
  • A merger or acquisition leads to a single company now using multiple clouds.
  • Some companies actively pursued a multi-cloud strategy, typically to realize better cost optimization.

(Reasons vary widely, the effect has been the same. According to Gartner, 75 percent of organizations will have deployed a multi-cloud or hybrid cloud model by the year 2020. Most of these models will include multiple infrastructure providers.) In other words, the move to multi-cloud often exists on a spectrum from purely incidental to fully intentional. A good multi-cloud strategy starts with where the organization is, whether it’s with a single cloud provider or multiple cloud providers.

Multi-Cloud is Growing but is Not the Same for Everyone

A July 2018 survey of over 600 decision-makers, conducted by Forrester, found that 86 percent of respondents had a cloud strategy they considered “multi-cloud.” But as we saw above, different organizations have adopted multi-cloud for different reasons. This means that the term “multi-cloud strategy” means different things to different companies.

Over 32 percent of those surveyed agreed that their multi-cloud strategy would best be described as “Using multiple public and private clouds for different applications workloads.” Only 10 percent referred to managing access from a single management portal. A meager 4 percent described it as developing applications with components deployed across different cloud platforms.

When is Multi-Cloud a Good Option for the Enterprise?

So let’s get down to brass tacks. If you want to be more intentional about your multi-cloud use, when’s the best time to make the transition? When is a modern multi-cloud approach appropriate?

A multi-cloud strategy is particularly appropriate for enterprises dealing with these kinds of challenges:

  • Users are distributed over a large area geographically, perhaps even internationally.
  • Users are located such that they often are not near an office or data center.
  • Regulations or security concerns provide reasoning for keeping some data and infrastructure in private clouds (or even on-premise).
  • The organization is likely to be the target of DDoS attacks that could stress infrastructure.
  • DevOps teams see a need for separate development and/or testing environments.
  • Demands for service are distributed geographically, making the distribution of workloads across different data centers a way to optimize performance.
  • Multiple cloud contracts already exist, and so access and management need to be centralized.
  • Multiple cloud contracts already exist, and costs are beginning to spin out of control.
  • The writing is on the wall, and you want to prepare your organization for a multi-cloud competitive environment.

Staying with a single cloud provider might be a strategy for smaller companies with very limited cloud computing needs. For most enterprise organizations, especially those with heavy technology needs, a solid multi-cloud strategy will beat single cloud adaptation.

Contact Connectria for more information.

Related Resources

 
IBM i Cloud Solution Maintains Momentum for Logistics Expert
In May, we discussed how remote management can relieve the “talent burden” as in-house IBM i experts retire. Another challenge Power Systems users face is…
 
8 Dos and Don’ts for Migrating Windows to AWS
When migrating Windows to AWS, the best way to reduce risk is to have a detailed migration plan in place. Migrations present both program management…