Cloud Computing: Understanding Infrastructure as a Service
Introducing the notion of an alternative to AWS: Cloudcenters
By: Randy Bias
Jan. 14, 2009 06:49 AM
Cloudcenters provide the same kinds of tools that all datacenter and server operators are already accustomed to, but with all the traditional advantages of cloud (i.e. self-service, pay-as-you-go, and scalability). Instead of creating completely new paradigms, cloudcenters are a methodology by which the customer can have a virtual datacenter hosted ‘in the sky.’
Amazon’s Web Services (AWS) is not the only way to build scalable Cloud Infrastructures. There are two emerging methodologies for constructing Infrastructure-as-a-Service (IaaS) AKA “Cloud Infrastructure Services”. The first is what we call “cloudcenters”, which are essentially datacenters in the sky. The second is what we call an “Infrastructure Web Service”. GoGrid was one of the pioneers for cloudcenters, while AWS largely created the second model.
Understanding IaaS means looking closely at these two approaches. Clearly the notion of cloudcenters embodied by AWS competitors such as ourselves, FlexiScale, ElasticHosts, AppNexus, and others is important. My colleague, Michael Sheehan, will go into more depth on how we think this distinction modifies his earlier Cloud Pyramid (above left) in a follow-on article to this one.
Understanding these two approaches is important because it directly affects your selection of a Cloud Infrastructure provider. These two models highlight a difference in core infrastructure and in target markets. Cloudcenters provide a direct equivalent to traditional datacenters and hence are usually more desirable for IT staff, systems operators, and other datacenter savvy folks. Infrastructure Web Services on the other hand are more analogous to Service-Oriented-Architectures (SOA), require significant programming skills, and are much more comfortable for software developers.
Infrastructure Web Services
I’m going to assume for this article that you are somewhat familiar with Amazon Web Services (AWS), but I’ll briefly re-cap. AWS provides a number of different ‘Web Services’ that can consumed individually or put together to support different kinds of applications, usually a batch processing or web application of some kind. These services include:
This is a robust ecosystem of services form which you can use any or all of in order to build your application, getting the traditional benefits of Cloud Computing such as self-service, pay-as-you-go, and massive scalability.
Unfortunately, every service above is based on an Amazon standard, not an industry standard. S3 is not accessible via CIFS or NFS. EC2 provides Xen hosting, but image management and storage is completely custom. SQS does not use any standard queuing or messaging protocols such as JMS or STOMP. SimpleDB now has an ‘SQL-like’ interface, but is essentially a 100% ground up creation of Amazon.
A major advantage of using the Amazon approach however is that greenfield applications developed from scratch have a very powerful set of vetted, scalable services, that can be used to build that application. This means avoiding the intrinsic and extrinsic costs associated with deploying a separate queuing or database system.
The alternative, of course, is to use the same tools, paradigms and standards that you deploy in an industry standard Enterprise datacenter today.
Reader Feedback: Page 1 of 1
SOA World Latest 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