What the hell is Hybrid Cloud?

Having worked in the IT sector for more than two decades I am aware that the devil lies as much in the definition of terms as in the detail of adoption rates. In this respect cloud computing is of course no different from any other IT marketing storm that we have experienced. However, the definitional bomb for Cloud computing is ticking away in an unexpected quarter.

The wrangling over definitions and Cloud to date has occurred in two main areas: the issue as to whether a “private” cloud is really a cloud if it doesn’t use shared infrastructure beyond the internal organisation; and then the old chestnut as to whether cloud must use a multi-tenanted architecture or not (For what it’s worth, my answer to both is yes). However, away from these disputes there is an ISV storm brewing regarding the use of the term hybrid cloud.
The problem has occurred because two distinct types of ISVs have started using the term to describe very different types of solution.
The pure-play definition of hybrid cloud
The pure-play cloud application providers use hybrid cloud in what I believe to be the correct sense of the term to refer to a cloud infrastructure that is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting). This is the term typically used by pure-plays to discuss integrating with platforms such as Force.com, for example.
 
This is the definition used by the US National Institute of Standards and Technology (NIST). It is also the definition used by the Cloud Security Alliance.
The mixed model definition of hybrid cloud
Traditional ISVs with an existing installed base using client-server implementations of their applications, are using a different definition of hybrid cloud – taking the term to either mean the integration of a cloud front-end application with a client-server back-end application, or to refer to the development of web-browser access for a traditional fat client-server application.
You say tom-ay-to, I say tom-ah-to, let’s call the whole thing off
On the face of it this seems such an esoteric discussion that it may not be worth having – at present cloud computing is a nascent deployment model in many organisations and many still struggle with how to define cloud computing itself, let alone fretting about a sub-set of cloud computing. But actually this definitional confusion is creating a number of problems for industry bodies and service-provider partnering strategies. This is because such bodies and service providers are working in an ecosystem with both cloud pure-play and traditional ISVs. And with such a large split in understanding and meaning of the use of the term hybrid cloud in the ISV community it is difficult to develop credible go-to-market approaches at a time when credible go-to-market approaches are sorely needed.
At K2 we’d be very interested to hear your views on this issue as well as any suggestions for terms to describe the different approaches, or indeed what you understand by the term hybrid cloud.

Comments

Definitions, definitions

I think it will take quite a while for definitions to settle down with the field being so young. I do agree that we need clarity and people should stop hyping things that are clearly not cloud!

Putting a web front end on a client/server app doesn't make it cloud - private, public, hybrid unless it makes it (almost) infinitely scalable, no entry barriers and pricing reflects usage.

One thing that I think will become really important is linking the public cloud to your infrastructure. For example Amazon have the Virtual Private Cloud. I don't think that is a good name either. To me it is public cloud with VPN gateway but that doesn't sound very catchy.

Perhaps we should call of these things a bastardised cloud as it's linked in a form of unholy matrimony but I can't see that catching on as a marketing phrase some how!
--
Twitter imcdnzl, Web http://iansblog.jandi.co.uk

Post new comment

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <p>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters shown in the image.