There’s an argument over whether the term “cloud” can be used to describe the changes taking place in internal IT architectures. How silly! Regardless of the term, there is a major trend playing out over the next few years where internal IT providers want to make fundamental changes so that they behave and provide similar benefits (on smaller scale) as cloud computing providers.
I believe that enterprises will spend more money building private cloud computing services over the next three years than buying services from cloud computing providers. But those investments will also make them better cloud computing customers in the future.
Building a private cloud computing environment is not just a technology thing – it also changes management processes, organization/culture, and relationship with business customers (our Infrastructure and Operations Maturity Model has a roadmap for all four). And these changes will make it easier for an IT organization and its customers to make good cloudsourcing decisions and transitions in the future.
We will even see several organizations evolve from being private cloud computing providers to becoming public cloud computing providers.
Can you find a better term? Go ahead. But you’ll be fighting an uphill battle. At Gartner, more and more of our clients are trying to understand what cloud computing can provide today, how it will evolve, what they should do now to prepare, and what they can learn from cloud computing. We are talking about private cloud computing on a daily basis. Get over it.
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.