I’m currently flying above 30,000 feet, well above a solid bank of confused clouds. Seems appropriate to think about the structure of cloud computing in the future.
Conceptually, cloud computing services can and will be provided at any layer of the IT computing stack, from raw compute services to business process services. So, conceptually, a cloud service might actually include a supply chain of cloud services – a cloud process provider using cloud software providers using cloud compute and storage providers, etc.
But that isn’t what’s happening today.
In these pioneer days, cloud service providers are doing it all. Software as a service providers are building data centers filled with customized infrastructure – and in Google’s case, highly customized and proprietary hardware. They are building, essentially, silos of vertically integrated solutions in the cloud. To be sure, these are cloud services, but why aren’t they using cloud services themselves?
One answer is that it is early, the supply chain, as such, doesn’t exist, and what does exist is not standardized. Another answer is that many cloud services are highly-focused and purpose-built (e.g., web search), and therefore underlying cloud enablers do not need to be general-purpose, and in fact, are more efficient if they are customized to do just a few things well.
But what happens when the supply chain starts to emerge? When standards improve for accessing services? What happens when the cloud service provider wants to expand into new businesses?
I believe that the future of cloud services will be much more dynamic and fluid, with both horizontal and vertical federation. While highly integrated and proprietary vertical cloud services will exist, they will be a minority – and in fact, their competition will be fluid, federated solutions of smaller competitors who should be much more agile. A future challenge for existing vertically-integrated cloud service providers will be to componentize their offerings – open up cloud services at lower levels of their cloud computing stack, and leverage other cloud service providers when appropriate. To be sure, they can differentiate by having customized hardware or unique management software, or unique performance capabilities – but betting on this differentiation going forward seems extremely risky as the markets mature.
This is exactly what happened to servers – they went from highly integrated and proprietary mainframes (proprietary hardware and limited applications) to midrange systems (with packaged software from third parties) to high-volume servers (hardware separated from operating systems separated from business applications). Mainframes have not gone away – but their role has certainly become a market niche. Mainframes have been attempting to evolve for years – to support more operating systems, more packaged applications, etc. This has slowed but not stopped a declining role for the mainframe in global computing.
Will Google and salesforce.com become the mainframes of the cloud? Will early market leadership translate into strategic viability even in a more componentized cloud services market? Will they invest strategically to avoid a vertically-integrated gridlock? Should Microsoft be building datacenters, or instead, directing datacenter standards for Microsoft software? Hmm…
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
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.