Gartner Zooms in on Key Cloud Computing AttributesBy eChannelLine | Print
Features common to all cloud computing solutions are services-based, elastic and scalable, and shared, among others, the firm said.
Cloud computing is moving into mainstream adoption, and Gartner has identified its five attributes, which can be used to see how strongly a cloud solution or service adheres to the cloud computing model.
"When approaching cloud computing, providers of cloud services and potential consumers of cloud services must examine the attributes of cloud computing to determine whether their services will deliver the expected outcomes," said Daryl Plummer, managing vice president and chief Gartner Fellow, in a statement. "If a service is not scalable and elastic, then it may not be shareable enough. If it is not metered by use, then it may not allow for flexible pricing. Support for more of the attributes opens the door to a great value proposition to the consumer, and greater flexibility and potential cost reduction for the provider."
Some services adhere to some attributes better than others, though.
"We recognize that services may adhere to some attributes more effectively than others," said David Mitchell Smith, vice president and Gartner Fellow, in a statement. "The degree to which the service exhibits all these characteristics indicates how much it adheres to the cloud computing model. One must examine a combination of these attributes to evaluate cloud services. Focusing on one attribute in isolation is not recommended."
The first of the attributes is that it's service-based. According to Gartner, "Consumer concerns are abstracted from provider concerns through service interfaces that are well-defined. The interfaces hide the implementation details and enable a completely automated response by the provider of the service to the consumer of the service. The service could be considered 'ready to use' or 'off the shelf' because the service is designed to serve the specific needs of a set of consumers, and the technologies are tailored to that need rather than the service being tailored to how the technology works. The articulation of the service feature is based on service levels and IT outcomes (availability, response time, performance versus price, and clear and predefined operational processes), rather than technology and its capabilities. In other words, what the service needs to do is more important than how the technologies are used to implement the solution.