Framing a Common Definition for Cloud Computing
|
The channel spent years deliberating and debating the true definition of what constitutes a managed service. I don't know if the issue was ever really settled or if the channel just got bored and moved on. Now that we're entering the era of cloud computing, the opportunity for renewed debate over cloud computing's definition. Frankly, I think we should skip it and follow the lead of the smart guys at the National Institute of Standards and Technology, who last week released a draft definition of cloud computing. NIST's Peter Mell and Tim Grance have come up with probably the best and most succinct definition for cloud computing I have yet to read. What makes it so good is that it's what I've heard many people say about cloud computing and Web-based applications all tidied up in one package. Here's what they wrote:
Their essential characteristics: On-demand self-service, broad network access, resource pooling, rapid elasticity and measured service. The three service models are software as a Service (SaaS), platform as a Service (PaaS), and infrastructure as a Service (IaaS). In their brief, Mell and Grance make all the usual caveats about how the actual implementation of cloud computing will change because of the large number of vendors, providers and applications involved, and that diversity will likely spawn unaccounted variations. However, they content that cloud computing will typically fall into this framework. Why is having a definition for cloud computing important? Not having a common frame of reference leads to confusion in the marketplace that ultimately creates obstacles to adoption, maturation and innovation. A couple of months ago I was hosting a roundtable of a dozen large enterprise CIOs on a variety of topics. When topic turned to cloud computing, these seasoned CIOs started talking about "the cloud," as if it were some magical medium. It was then that I started talking about the different kinds of clouds that will comprise the new online application and infrastructure delivery world. What do you think of Mell and Grance's definition? Does it fit the cloud computing you know? Or is this draft missing something? |
Comments (5)
Great summary and thanks for pointing this out. They also have some very good ppt overview of cloud computing :http://csrc.nist.gov/groups/SNS/cloud-computing/index.html
And I have to say that it tops my humble shot at a cloud computing definition:http://bobolwig.wordpress.com/2009/06/14/yada-cloud-computing/
Posted by Bob Olwig | August 26, 2009 6:08 PM
I think it is great. Until someone comes up with a better one, I'm going to use and promote Mell and Grance's definition.
Posted by Gary Lesperance | August 27, 2009 11:25 AM
Excellent and succinct definition. Anyone care to take on the definition of SaaS? What makes it different (if it is) from a hosted application available to users over the internet or intranet, using a web interface?
Posted by Lee Knoch | August 27, 2009 12:19 PM
The creation of an official - albeit evolving - definition of cloud computing is a further sign that cloud hype is starting to translate into legitimate models with real-world use cases.
A critical item that Mell and Grance may want to consider adding to their definition is a graphical representation of cloud computing models similar to the industry’s OSI networking infrastructure reference model. An industry standard architectural description for the layered components within each cloud service model (IaaS, PaaS, SaaS) and deployment model (Private, community, public, and hybrid) would further reduce the hype by driving vendors to clearly articulate their product offerings within a particular “cloud stack”.
For Platform Computing, the private IaaS cloud stack is most relevant, and we recommend the following: a base layer comprised of servers, storage and network components. The second layer would include VM managers and provisioning tools, which are topped by a third layer comprised of resource integration tools. The fourth layer is the allocation services, and the fifth and final layer is the service delivery layer – as a whole enabling elastic infrastructure services to applications and end users.
We welcome your input on further articulating and demystifying the cloud “stack.”
Posted by Randy Clark, CMO, Platform Computing | September 1, 2009 9:43 AM
I think this is a very good definition although I would have preferred to see something about the commercial differences in a cloud computing model - i.e. pay per use. Whilst it's implied, I think it would have made the definition more complete.
I am interested however in the role of a channel in cloud computing. I am in the process of segmenting the cloud computing market for some research that I am carrying out. And I feel that I want to add a channel component to the segmentation but I'm not sure I understand the role that the channel will play once the market matures.
I can certainly see a channel model of sorts for applications that are built using cloud infrastructure services (such as Amazon’s) or using Platform Services (such as force.com) and then made available to the consumer. I can also see a genuine channel model for Cloud Software vendors who sell “real” software products to Cloud Service Providers who then make some service or other available to the consumer. But right now I don’t see a real model for a conduit of Cloud Services outside of some sort of introduction / introductory fee model.
Do you have any further insight into the structure of current/likely channel models for cloud computing?
Thanks in advance
Danny Goodall.
Lustratus REPAMA Marketing Analysis and Consulting
Posted by Danny Goodall | September 1, 2009 10:41 AM