The difference between Hybrid & Multi-Cloud for the Enterprise
(c) 2017 AVOA/ Tim M. Crawford | http://avoa.com/

The difference between Hybrid & Multi-Cloud for the Enterprise

Cloud computing still presents the single biggest opportunity for enterprise companies today. Even though cloud-based solutions have been around for more than 10 years now, the concepts related to cloud continue to confuse many.

Of late, it seems that Hybrid Cloud and Multi-Cloud are the latest concepts creating confusion. To make matters worse, a number of folks (inappropriately) use these terms interchangeably. The reality is that they are very different.

The best way to think about the differences between Hybrid Cloud and Multi-Cloud is in terms of orientation. One addresses a continuum of different services vertically while the other looks at the horizontal aspect of cloud. There are pros and cons to each and they are not interchangeable.

Multi-Cloud: The horizontal aspect of cloud

Multi-Cloud is essentially the use of multiple cloud services within a single delivery tier. A common example is the use of multiple Public Cloud providers. Enterprises typically use a multi-cloud approach for one of three reasons:

1)    Leverage: Enterprise IT organizations are generally risk-adverse. There are many reasons for this to be discussed in a later post. Fear of taking risks tends to inform a number of decisions including choice of cloud provider. One aspect is the fear of lock-in to a single provider. I addressed my perspective on lock-in here. By using a multi-cloud approach, an enterprise can hedge their risk across multiple providers. The downside is that this approach creates complexities with integration, organizational skills and data transit.

2)    Best of Breed: The second reason enterprises typically use a multi-cloud strategy is due to best of breed solutions. Not all solutions in a single delivery tier offer the same services. An enterprise may choose to use one provider’s solution for a specific function and a second provider’s solution for a different function. This approach, while advantageous in some respects, does create complexity in a number of ways including integration, data transit, organizational skills and sprawl.

3)    Evaluation: The third reason enterprises leverage a multi-cloud strategy is relatively temporary and exists for evaluation purposes. This third approach is actually a very common approach among enterprises today. Essentially, it provides a means to evaluate different cloud providers in a single delivery tier when they first start out. However, they eventually focus on a single provider and build expertise around that single provider’s solution.

In the end, I find that the reasons that enterprises choose one of the three approaches above is often informed by their maturity and thinking around cloud in general. The question many ask is: Do the upsides of leverage or best of breed outweigh the downsides of complexity?

Hybrid Cloud: The vertical approach to cloud

Most, if not all, enterprises are using a form of hybrid cloud today. Hybrid cloud refers to the vertical use of cloud in multiple different delivery tiers. Most typically, enterprises are using a SaaS-based solution and Public Cloud today. Some may also use Private Cloud. Hybrid cloud does not require that a single application spans the different delivery tiers.

The CIO Perspective

The important take away from this is to understand how you leverage Multi-cloud and/or Hybrid cloud and less about defining the terms. Too often, we get hung up on defining terms more than understanding the benefits from leveraging the solution…or methodology. Even when discussing outcomes, we often still focus on technology.

These two approaches are not the same and come with their own set of pros and cons. The value from Multi-Cloud and Hybrid Cloud is that they both provide leverage for business transformation. The question is: How will you leverage them for business advantage?


Originally published on AVOA: https://avoa.com/2017/10/17/the-difference-between-hybrid-and-multi-cloud-for-the-enterprise/

Definition for Hybrid Cloud should be elaborated to understand the effectiveness in today's world. An ideal example would an ecosystem available across on-premises, private cloud and public cloud services. This gives a flexibility to cater computing resource management and effective cost variations. Technically it widens the deployment options benefiting the customer.

Like
Reply

If We have combination of on premise+Few Application hosted over Cloud(AWS, Azure etc), that's also an example of Hybrid Cloud. Agree with Multi-cloud representation.

Like
Reply

This is not accurate and a bit insulting to the illuminati. Slapping Azure to everything does not make it so. Any corporate/legacy data center can be integrated with any cloud provider and all cloud providers have applications that provide services using the cloud. What this picture shows is that cloud backbones can be provided by multiple platforms and leaves out that AWS is the de-facto inventor of cloud computing as we know it.

Really, vendor names need to be removed and substituted with variables, to reflect the real future, an agnostic one. The future Cloud of Clouds will make specific technologies and vendors less and less important over time. Especially if AI is used to determine where the best location is to host an application, based on real, objective values for cost, latency, sla compliance, interchangeability, etc. AI selection of where to run code will not be swayed by past certifications or human bias, and will lead to the real lowest cost to provide services. Coders will want to create code that is the most flexible in where it runs, because future services will accept code only from coders with high reputation for bug-free code, fast code, interchangeable code. Can't you all see it? The line of 'Meta' services keeps moving higher and higher into the IT food-chain... First, we built things on specific hardware, the virtualized it, then we virtualized the data centers, and next we'll virtualize the Clouds, and eventually, it will just be about Service delivery, and the rest behind the scenes will be managed by AI... Heck, all code may someday soon be AI developed... I should write a book on this...

The Micro services API economy helps in integration.

Like
Reply

To view or add a comment, sign in

More articles by Tim Crawford

Others also viewed

Explore content categories