Cloud Computing: What It Is and What It’s Not
The logical next step in dynamic infrastructures and architectures
By: Bill Bauman
Feb. 4, 2010 03:30 PM
Cloud computing is a concept. It is an architectural framework by which one or many organizations can deploy, manage and retract any workload, public or private. Cloud computing addresses business needs from a workload perspective. The concept collectively addresses all the aspects of modern computing from components (SAN, network, servers, software) to implementations (virtual desktops, hosted applications, e-mail, etc.) in a comprehensive, cohesive solution.
What It Is
The buzzword-laden and slightly more complete definition:
A cloud is a dynamic, infinitely scalable, expandable, and completely contractible architecture. It may consist of multiple, disparate, local and non-local hardware and virtualized platforms hosting legacy, fully installed, stateless, or virtualized instances of operating systems and application workloads.
What It Is Not
Marketers seem to be struggling with how to position and sell cloud computing and the offerings based on it. This is leading to many misrepresentations of what a cloud is. Most of the cloud computing solutions being marketed today are merely hyped up hyperbole of Internet-based or Web 2.0 computing. These solutions and offerings are components of what a cloud computing architecture would represent.
Amazon's online resource offering, EC2, is a good example of the common divide between marketing and technology. Amazon's site defines EC2 as: "Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizable compute capacity in the cloud." It would more appropriately be defined something to the effect of "... is a web service based on Amazon's cloud computing architecture that provides resizable compute capacity to its users via the Internet."
The Internet is not "the cloud," yet that seems to be the most common misuse of the term. This misuse is confusing business people as to what the cloud really is and technology professionals as to how a cloud is useful within their organizations. As a technology professional, it is important to understand that cloud computing has benefits and applications far beyond large web service and hosting providers.
This does not preclude cloud computing from use in Internet-based solutions. Amazon's EC2 and Google Apps are good examples of this. The technologies used to deploy these systems are either heavily or entirely cloud-based. The systems are dynamic, extensible and expandable. They may or may not exhibit all of the qualities of a true cloud computing architecture, but they certainly qualify as being cloud-based.
Another misconception of clouds is that they are exclusively public, private, internal or external. Based on its definition, cloud computing is a construct to implement any of those solutions, independently of each other or inclusive. A properly designed cloud computing architecture could allow an organization to dynamically deploy, manage and retract internal, external, public and private workloads.
Although a public and a private cloud could be one and the same, most commonly, if a cloud computing architecture is implemented to offer billable, service-based offerings to external users or customers, it is being considered a public cloud. Likewise, it is becoming commonplace to refer to cloud computing architectures that only offer compute services to internal employees as being private clouds.
Cloud computing is fast becoming fantastic marketing jargon for companies and organizations that may or may not have the capability or the desire to really explain it or deliver on its promise. It is not an easy concept to grasp. The more abstract a concept is, the harder it is to explain; and even harder to properly implement. Cloud computing is an abstract concept that includes the implementation of multiple abstract technologies. All of the intangibles involved make explaining cloud computing difficult, but poor explanation should not minimize what cloud computing can accomplish.
How We Get There
Cloud computing is accomplished with a building block approach. Start with the base reference architecture. Install the underlying tools to deploy, manage and retract the resources on that architecture. Then add the necessary components (hardware and software) for the workloads that a particular cloud needs to support. As workloads requirements increase, additional building blocks are added to the cloud.
What about traditional operating system (OS) deployment tools? What about application deployment and orchestration tools? These legacy tools are part of the building blocks that get added to a cloud computing architecture. On their own, they do not constitute a cloud. They are part of the components that provide the ability to add and customize workloads within the cloud.
One of the major requirements of cloud computing is that the underlying tools to deploy, manage and retract the resources in a cloud must be indefinitely scalable. If the underlying architecture is not scalable beyond any known capacity, then the design could be limiting.
Reader Feedback: Page 1 of 1
Latest Cloud Developer Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week