The benefits of cloud computing continue to grow

In May of 2010, I wrote my first article dedicated to explaining the benefits of cloud computing (check out that dated graphic on that page).  I updated that article in August of 2012.  Now, it’s time for another update, or really,  more of an addendum.  The cloud industry has been unfolding for quite some time now and it’s clear that it’s not a “flash in the pan” or some trendy thing that will die.  In fact, it’s more relevant today than ever before!  In addition, there are more players and new technologies.  And, more importantly, the value & benefits continue to grow.

Patch Management in the Cloud

I was on my way to a lunch appointment when I started thinking of the headache of managing patching in the cloud.  More importantly how would you ensure that your template server that is used to clone for new servers is current?  

To resolve this, I’d love to see a cloud provider offer the ability to patch the dark VM on disk and if you have a local cloud, say using vmWare, do the same thing to your VM on disk.  After all, there’s an exploit to go directly to a VM image, why not a program that will scan that disk image?

Quick Review and Comparison of Rackspace

Rackspace, a cloud infrastructure as a service (IaaS) vendor, has been ramping up their advertising and recently announced that they were giving away their cloud management software for free for use in private clouds.  Given all the activity and buzz in the media about Rackspace and OpenStack, I thought I’d give Rackspace a test run.  I used the same approach that I used in my Amazon AWS review and setup an application on their cloud for a semi real-world trial.  Given that I’ve used AWS, I’ll try to do some quick comparisons as well. 

NASA Mars Mission Uses Amazon’s AWS

NASA’s use of Amazon’s AWS is interesting.  I knew that NASA had a private cloud so I didn’t expect them to use AWS.  I’m guessing this is a good example of using the cloud to augment capability quickly when you don’t have enough (cloud bursting) and take advantage of services that are too costly to build yourself.  NASA was able to quickly setup needed AWS EC2 services to prepare and serve images and then take advantage of Amazon’s huge network footprint to cache images on the edge of the net to serve images and other science data to a massive set of customers around the globe.

Cloud Vendor Expansion

After taking a much needed vacation I thought I would post an update to catch up on some notable events.  Although Google has been in the cloud business as a “software as a service” (SaaS) provider with their office productivity apps, and a “platform as a service” (PaaS) provider with Google App Engine, they entered the infrastructure as a service (IaaS) field in June, firing a shot over the bow of Amazon, who for the most part is way ahead of everyone in experience and number of products.  HP announced their cloud offering as did Oracle.  All of the new entrants were at limited release status when they made these announcements.

The Step Function of Cost

Building a “Private Cloud” within your data center has a lot of potential return on investment (ROI).  David Linthicom’s article, and others, are saying “you need to architect”.  

The focus needs to be on the architecture and the right-fitting enabling technology, including both private and public cloud technology, and not gratuitous opinions. There should be no limits on the technology solution patterns you can apply. If that means private, public, or a mix of both, that's fine as long as you do your requirements homework and can validate that you have chosen the right solution.

I agree, just stop architecting with brochure-ware and really think through your solution.  Think about what you need today, where you are going and how you integrate everything else.  Excluding software as a service (SaaS), when you compare private and public clouds there are some real advantages for a private cloud.  One of the biggest advantages I see public cloud solutions have, is the flexibility to scale up and down and time it takes to do that.

The thing I keep coming back to when I talk to people about public vs. private clouds is what I call “large step functions in cost”. One of the big step functions is cost to build a data center or enlarge it.  That large investments in infrastructure kills your ROI until you fully utilize that capital investment.  If you are building (or enlarging) a data center for example, most companies don’t build just what they need today, they leave some room for growth, and that’s “flexibility”.  That flexibility is costly because it just sits there on the books not really giving you any ROI until you start using it.  Really the ROI from that flexibility is only realized as future cost avoidance of the next step function in cost.  It’s like buying a restaurant and initially only serving breakfast.  Sure you’ll eventually staff up and start getting better use of that capital investment when you start serving lunch and dinner but until you do, your ROI may be negative.  Compare this to the cloud where having the capacity to grow costs you nothing.  Is “public cloud” always the best solution?  No, but you have options, architect, think, and compare.

- Chris Claborne

References & Related

• Benefits of Cloud Computing


• Challenges & Risks of Implementing Cloud Computing

How to Get Started With Cloud Computing

Some IT departments want to utilize public cloud infrastructure as a service (IaaS), or Software as a Service (SaaS) but aren’t sure how to get started.  I’ll discuss some ways to use cloud computing as you flesh out how you will use it and integrate into an existing information technology architecture.  If you’re not sure what IaaS is, read my previous article, “Exploring Amazon’s Cloud IaaS & PaaS”.

Using Amazon’s AWS

In my last article, “Exploring Amazon’s Cloud IaaS & PaaS”, I introduced Amazon Web Services (AWS), and I used AWS to describe the terms “Infrastructure as a Service” (IaaS), and “Platform as a Service” (PaaS).  In order to better understand the value of AWS, I deployed a real world application.  In this article, I’ll step through how I deployed and scaled my example application on AWS and comment on where I found the greatest value to be.  If you haven’t read my first AWS article, “Exploring Amazon’s Cloud IaaS & PaaS”, I suggest you read it as an introduction to AWS.

Gartner Has First Ever IaaS Magic Quadrant Report

From ReadWrite Cloud's David Strom,  "Gartner Has First Ever IaaS Magic Quadrant Report"

A new Gartner Magic Quadrant report is available this week covering the public cloud computing vendors. Not surprisingly, AWS received top honors, although Terremark, Savvis and CSC were also praised. Bluelock, a smaller vendor, also got props. The report is very detailed in the usual Gartner manner and is a must-read for enterprise IT architects who are evaluating players in this space.

I don't have access to the report but am interested to read it.

Exploring Amazon's Cloud IaaS & PaaS

Amazon Web Services (AWS) is a large offering of various compute and applications services that I will use for this article to help describe what “Infrastructure as a Service” (IaaS) and “Platform as a Service” (PaaS) are.  

AWS is used by many large Internet companies like active.com, Ericsson, the guardian news, Yelp,  IMDB and others to deliver their web applications or services.  Although I’ve covered Software as a Service” and related benefits, risks, and some specific applications, this article will take the next big step into another side of cloud computing, using public scalable infrastructure to deploy your in-house applications.