by Neil MacDonald | July 15, 2011 | Comments Off on Seven Cloud Computing Pet Peeves
1) Treating Cloud as one thing.
At a minimum, clarify whether you are talking about SaaS, PaaS, or IaaS – and whether you are talking about public or private cloud implementations.
2) Assuming Cloud always means Public Cloud
Cloud is a computing style, not a location.
3) Citing Security as the number one issue to the adoption of Cloud without digging deeper.
“Security” is too vague. “Cloud” is too vague. Combined, this statement is pretty much meaningless. See #1 above. Cloud isn’t one thing, so securing the Cloud can’t be one thing either.
4) Equating virtualization to the Cloud
Virtualization is a stepping stone for Cloud, especially in enterprise data centers but is not required for Cloud computing.
5) Assuming Cloud is always less expensive.
In most cases, the driver is speed and agility, or that the cost is OpEx not CapEx. Overall costs are likely to be the same or higher.
6) Assuming that moving to the Cloud gives my application resiliency.
If you have a critical application, the move to the Cloud doesn’t automagically endow your application with resiliency. You have to architect for this. Amazon AWS users found this out the hard way.
7) Referring to traditional hosting as “Cloud”
Many deployments of Microsoft’s BPOS and now Microsoft’s Office 365 use Microsoft’s “dedicated” offering with servers dedicated to the enterprise, but run by Microsoft. Call it what you will, but this is traditional hosting under the Cloud moniker.
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.