My last blog entry caused quite a ruckus. While the term “private cloud” has been in use for at least a year, there are still semantic, moral and religious issues with the term. I respect the issues, but I have also found the anti-private-cloud zealots to be a minority. In the past week alone, I met with fifteen different companies (vendors and users), and most of the conversations revolved around the private cloud concept. All of the vendors are embracing the term (no surprise). More importantly, the users were also embracing the term, the concept, and the strategy.
So how do you know you’ve arrived? What is different from a private cloud versus a well-run IT organization?
- Services-oriented. The IT organization sells services, and the IT customer only deals with IT through service offerings (self-service).
- Variable Pricing. Based on usage. The IT organization maximizes technology sharing and automation for efficiency.
- Elasticity. Customers deploy/grow/shrink/retire services quickly. IT is architected to ensure fluid scaling on demand.
- Independence. The IT organization could move a service to the public cloud by flipping a switch. Likewise, the IT organization could choose to open their services to external customers easily. I even talked to a company today interested in take their services “public” sometime in the future.
There are probably many more, but I think this captures the essence. What am I missing?
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.