Wednesday, July 27, 2011

PaaS is a Cloaking layer for clouds

We seem to be coming to the end of the definition of Platform as a Service (PaaS) blog posts and are now moving on to the more pressing question of what is PaaS good for?

In a recent Paul Maritz talk at GigaOm Structure conference, he referred to PaaS as "a cloaking layer for clouds." This is an elegant definition for a rapidly expanding market of add-on cloud services.

If Cloud 1.0 is a set of servers in the sky (think Amazon EC2), then Cloud 2.0 is a layer of services that hide the complexity of developing, deploying and managing applications in the cloud (think CloudFoundry).

The API for Cloud 1.0 is the virtual machine/OS. The API for Cloud 2.0 is the application container itself - services like CloudFoundry, Elastic Beanstalk from Amazon and Heroku allow a developer to hand over an application to the application container without having to know anything about what operating system that application is running on or how it communicates with other services like load balancing, failover and database.

Here are several examples of PaaS cloaking to simplify cloud development:
  1. Dev/test environment: WaveMaker pioneered the market for cloud-based development of standard Java applications. In addition, simply virtualizing the provisioning of servers has huge value for development and testing purposes. Today, this is a major driver for developer adoption of cloud in general and PaaS in particular. I have talked to CIOs who claim that over 30% of their resources for new projects goes into provisiong and managing the dev/test environment.
  2. Scalable application deployment: Amazon EC2 has made its mark by providing a highly scalable data center in the sky. Zynga uses Amazon as a safety net when it has no idea how popular one of its games will be. Once Zynga has a handle on demand, they move the game over to their own data center. Just a year ago, getting this kind of scaling required detailed understanding of cloud architecture and a whole lotta scripting. Now it's as easy as "vmc push --instances 8"!
  3. Resilient application deployment: infinite scaling is great, but what happens when a network configuration error brings down in your infinitely scalable data center? In that case, having a PaaS service that automatically mirrors applications across multiple data centers makes a critical difference.
In a sense, PaaS is just a new kind of virtualization, one that operates at the level of an application container instead of an operating system. No wonder then that VMware has a lot of firepower to bring to the PaaS market.


Anonymous said...

..and Datbase.

i'm not sure if i like this. It's an potential Vendor lock-in!


Christopher Keene said...

The lockin would only come if: 1) you were not able to move to a different cloud and 2) you had to pay for the PaaS layer itself.

With CloudFoundry, both of these potential lock-in concerns are elminated: 1) CloudFoundry can target any cloud and 2) CloudFoundry is free and open source!

Anonymous said...

I agree if moving the data is possiblen.

For a large amount (TB's)of data you got locked-in because there's now way to move the data within a reasonable timeframe.

AWS import/export services is a solution using the old snail mail method. Maybe implementing CF snail mail could be a consideration? ;-)


us vpn said...

I agree with anonymous, it's a lock-in for sure.

data center said...

Wave Maker is a major driver for developer adoption of cloud in general and PaaS in particular. It helps in communication other services like load balancing and database in data center.