Gartner Blog Network

Partly or Mostly Cloudy?

by Tom Bittman  |  October 9, 2008  |  4 Comments

My head has been in the clouds for the past week or so – I’ve literally been working full-time on cloud computing. Cloud services are popping up right and left, and more are coming. Some of these are not cloud by our definition. But what about the ones that fit the definition, but barely? From a cloud customer perspective, what makes one service more “cloudy” than another?partlycloudy

I think there are two obvious dimensions to “cloudiness”: Service and Elasticity. There is a third less obvious dimension that I’ll talk about later.

By definition (ours, at least), cloud services are services-oriented, but how much? At one end of the spectrum, a cloud service is highly standardized, uniform, one-size fits all. A service, but not very rich – probably designed more for high-volume and reach. I’m thinking John Belushi on SNL saying “No Coke – Pepsi!” At the other end, a cloud service is highly customized to meet cloud consumer needs, perhaps with a wide range of quality of service options – like Burger King’s “Have it your wayyyy!” (OK, that’s just marketing, but you know what I mean). In the early days of cloud computing, most cloud services will tend to be relatively simple, with limited options. As cloud services mature, more and more personalization and choices will emerge.

Elasticity is also a requirement, but how elastic? At one extreme, elasticity might be slow, or come in chunks. It might be difficult, and require some intervention. It might reach some low-end or high-end scale limits. There might be a high barrier to entry, or high barrier to exit. Kinda sorta elastic. At the other extreme, elasticity is rapid, very smooth and granular. Entry and exit are easy. Sourcing could dynamically move from one provider to another. The nirvana of utility computing. Early cloud offerings have elastic qualities, but they also have a long way to go. With Amazon EC2, for example, you need to define the size of server you need. You can add another one, but it takes a little intervention. This too shall pass.model

I think there is another dimension, but I am struggling to name it (please let me know if you have ideas). Let’s call it market, for lack of a better term. At one end of the spectrum, a cloud service is highly monolithic, built on a customized architecture, an integrated top-to-bottom solution, perhaps less innovative and dynamic. A relatively closed market. I discussed this kind of cloud service in my last blog post. The other end? A cloud service built on top of cloud services, an ecosystem of services working together, very organic and dynamic. An open market of federated providers, constantly changing. These are quite rare today, but I expect more to develop over time.

The early cloud service providers are building castles in the clouds. Frankly, in these early days, we need to start this market with a few successful castles. But I expect dynamic and vital markets to bloom around and away from the castles as cloud computing matures. I also expect those monolithic providers to evolve to interact with the market at many different levels – but not right away. Will always have their own data centers? Do they want to? What about Microsoft? Maybe now, but later, after the market evolves? We will see.

Additional Resources

View Free, Relevant Gartner Research

Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.

Read Free Gartner Research

Category: cloud  

Tags: amazon  cloud-computing  elasticity  google  microsoft  

Thomas J. Bittman
VP Distinguished Analyst
20 years at Gartner
31 years IT industry

Thomas Bittman is a vice president and distinguished analyst with Gartner Research. Mr. Bittman has led the industry in areas such as private cloud computing and virtualization. Mr. Bittman invented the term "real-time infrastructure," which has been adopted by major vendors and many… Read Full Bio

Thoughts on Partly or Mostly Cloudy?

  1. I’m wondering if you have any thoughts to share about customization that goes beyond the features and functions of the service platform?

    Isn’t it possible to add meaningful value by offering flexible service level agreements, as an example?

    A willingness to adapt the terms an conditions of a typical contract is one area where creativity might differentiate a provider in the marketplace.

  2. Tom Bittman says:

    Absolutely – that’s what I meant by quality of service. I believe the whole idea of an SLA will by necessity become more flexible for some enterprises/workloads – high availability needed today, not tomorrow, better performance during a peak competitive period, less performance later, etc. Somewhat the opposite of typical outsourcing SLAs today, where change is slow and painful. And, of course, there will also be the opposite – good-enough, standard, uniform, up almost all the time service. And for many enterprises/workloads, that will be absolutely fine. Agree?

  3. […] (Can A Cloud Computing Provider Be Too Massive?, Is Google the Mainframe of Cloud Computing?, Partly or Mostly Cloudy?) and I’m getting more and more comfortable talking about three major phases of market evolution. […]

  4. […] and managed on specific on-premises platforms,” says Thomas Bittman, a Gartner analyst, on his blog. “Not to say that Amazon, Salesforce or Google have all the kinks worked out–but they […]

Leave a Reply

Your email address will not be published. Required fields are marked *

Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.