Flight Plan: Cloud Computing Meteorology
Posted on 01. Nov, 2009 by vbrown in Cloud Computing, Enterprise Architecture, Feature
There are so many voices expressing confusing and diverse opinions around the topic of Cloud Computing. Definitions, benefits and risks, strategies for adoption, are all over the map. Most have some merit; very few make practical sense and are actionable. My goal in this series is to provide fundamental definitions and practical strategies that can be adapted in your context. I think that “Cloud Meteorology” is an apt term – referring to the types of clouds and what we can expect from each.
In my previous post about Cloud Computing strategy I reviewed the NIST’s definition of Cloud Computing which, by the way, is achieving wide acceptance in both private and public IT. It includes the characteristics that identify a Cloud, and that differentiate it from its close cousin, the virtualized computing platform.
Cloud Models
Now let’s review the models that will guide you in adopting an appropriate Cloud strategy and implementing the most effective platform. NIST defines three cloud Service Models. I think that it’s important to realize that these are general definitions and the lines between them can be blurry.
The Service Models are:
Cloud Software as a Service (SaaS). The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). [Vic] Some well-known examples include Google Apps, Salesforce.com, and NetSuite.
Cloud Platform as a Service (PaaS). The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure. . .
Cloud Infrastructure as a Service (IaaS). The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications.
These Service Models can serve as a guide to understanding the types of services currently being offered by commercial service providers. (We’re most familiar with the commercial SaaS offerings — Google, Amazon, etc. — but vendors offer solutions in all three layers.) The models also provide guidance for structuring your “private” or “community” Cloud platforms.
Next. . .
My next post will wrap up the fundamental definitions by defining a set of deployment models (architectures) for implementing Cloud platforms – primarily for enterprise Clouds as opposed to commercial SaaS offerings. Then we’ll begin exploring roadmaps to the destination. I’ll offer some suggestions for reducing complexity that allow you to develop a more clear and relevant Cloud Computing strategy in your context.
In future posts in this series we’ll address other closely associated topics, e.g., SOA, BPM. I’ll talk about their significance in a Cloud strategy and how they can be leveraged to deliver a powerful and flexible IT ecosystem. I’ll suggest some detailed roadmaps that can lead to early benefits along the path to your target, ensure that you manage and mitigate risk, and that lay a solid platform for a sustainable ecosystem.
Recent Comments