Comparing AppEngine , EC2 and Caroline

I gave a talk to the Los Angeles Java User group on the topic of "Comparing Google App Engine , Amazon Webservices and Project Caroline".

A lot of what I presented was really distribution of existing content and discussions. The only unique perspective that I think I added was the slide below.

The way I look at any player in the Cloud Computing space is one of the four buckets

1. Bare Metal - People and Process driven , essentially traditional style with some Hypervisor - the only service opportunity here is the traditional EDS type outsourcing that utilizes skilled labor and pooled labor.

2. HaaS - Hardware as a Service. My Definition: Programmatic Interface for Hardware Provisioning . EC2 fits in perfectly here. Moves up from BareMetal as it minimizes on "People Services" and focuses on Pooled hardware capacity and real-time provisioning of hardware. Typically billed by Clock time - offers a lot of flexibility in terms of choice of language runtimes.

3. PaaS : Platform as a Service . The issue of scaling has been abstracted out by the Platform and you have flexible services that automatically provision computing. Also refered to as Fabric . App Engine is an excellent example here. Another interesting point here is that you billing will typically move from Clock time to CPU cycle time - because there is no longer some instance you need launch.

4. SaaS : software as a service. Gmail , salesforce.com , ebay etc. You basically do not care what is happening beneath the stuff. You are the consumer of the software and expect the application to run





Here is the full Presentation.

Cloud Computing

View SlideShare presentation or Upload your own. (tags: ec2 appengine)