Flight Plan: Deploying the Cloud
Posted on 06. Nov, 2009 by vbrown in Cloud Computing, Enterprise Architecture, Feature
The early phases of a new technology paradigm are disruptive and confusing. And the confusion usually starts with words and the difficulty of clearly communicating complex topics! That’s definitely true of the cloud computing paradigm. The term “Cloud Computing” is applied to a wide variety of applications and (sometimes contradictory) definitions.
This post wraps up what I hope is a clear, comprehensive working definition of Cloud Computing. The goal is to provide a basis for deeper exploration into the applicability and appropriate use of Clouds as a component of an enterprise IT strategy.
In previous posts in this series, I offered two aspects of the definition of Cloud Computing established by the National Institute of Standards and Technology (NIST)
Cloud Deployment Models
In this post I will talk about the final aspect of the NIST definition…the four Deployment models. These variations in Cloud deployment are often the most misunderstood and yet most critical to developing an effective Cloud Computing strategy and roadmap.
NIST Cloud Computing Deployment Models
Private cloud. The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.
Public cloud. The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services. This is the most well-known and easily-recognized model of Cloud Computing – Google, Amazon, Salesforce.com, and many, many more.
Community cloud. The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise.
Hybrid cloud. The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds). [Note] As the use of Cloud Computing matures, I believe the Hybrid Cloud will be the most common model.
Here’s a graphic illustration of how a large enterprise might (and very likely, would) leverage all four of the models.
Cloud Deployment
Next . . .
In my next posts, I’ll talk about some proven best practices and lessons learned, from my experience and from documented industry success stories. I’ll offer some suggestions for reducing the complexity that allow you to develop a more clear and relevant picture of Cloud Computing in your specific context. I’ll address the concerns that are most often raised about security, availability, and performance, and solutions for resolving each.
Along the way, I’ll discuss other associated topics, for example, SOA and BPM, and how they can be leveraged to make your Cloud strategy even more effective. And finally, I’ll provide some general roadmaps for moving into the clouds that factor in all of these aspects and that include strategies for risk management.
Recent Comments