A Case for Private PaaS

by Jani on July 29, 2010

A couple of weeks back, at the IBF Panel discussion on PaaS, we were discussing the opportunity for a Private PaaS. While a Private Cloud is typically associated with IaaS, I started to ponder on the value of a Private PaaS offering.


Installing the development platform / runtime running .NET or Java stack on a set of VMs provisioned on the Private (IaaS) Cloud doesn’t turn it into a Private PaaS. PaaS should really abstract the nuts and bolts of the infrastructure (OS, middleware and other plumbing) and should expose only what is required for the applications to run.

Microsoft’s announcement of Windows Azure Appliance at WPC underscores the significance of the Private PaaS. This appliance will remove the overhead of maintaining and running an environment to host applications. VMware is aggressively positioning it’s Spring framework on both Private and Public PaaS offerings. AppScale, the open source implementation of Google App Engine on EC2 and other standard VMs has a huge potential to become a Private PaaS. IBM WebSphere Cloudburst Appliance is another implementation of the Private PaaS. These appliances come with complete self-service capabilities and reduce the provisioning of development, test and production environments from days to few hours.

Let’s take a look at the scenarios and potential customers for the Private PaaS –

  • Service Providers / Managed Data Centers – These are the next generation ISPs and companies who are into managed data center operations. By deploying PaaS in a box, they can focus on delivering the service to its customers vs. managing it. The multi-tenant capability which is core to the PaaS appliance will provide an isolated snapshot of the environment to the PaaS consumers.
  • System Integrators – Large System Integrators who offer turnkey IT solutions can now offer PaaS to their strategic customers. This will enable SIs to deliver an end to end solution to the customers. System Integrators can now offer SLAs which are covered by the PaaS appliance providers. Customers will see value in this deal because the SI will own the entire lifecycle of the solution. This will also address the data security and compliance issues by keeping the sensitive data within the political boundaries of the country. I personally see this as a huge opportunity for the System Integrators in India.
  • Large Enterprises – Large automotive, manufacturing and finance companies with presence all over the globe will be able to benefit from these PaaS appliances. By deploying a few in strategic locations, they will be able to reduce the maintenance cost of running Line of Business applications.
  • Government – One of the niche customers of the PaaS appliance would be Government. By deploying state level appliances, the government will be able to create a secure Government Private Cloud. Since this runs within the premises of the government data centers, compliance and regulatory issues will not be a concern. Government can confidently store the data and run applications running a set of appliances deployed across the country.

This is an interesting space to watch. Do you see the potential for Private PaaS?

[This article was originally published in the Cloud Computing Journal]

  • http://twitter.com/mvisser Maarten Visser

    The potential for Private PaaS is indeed huge! Private PaaS is THE answer to all those organizations who like the bennefits of a Cloud OS, but are scared about privacy and security…

  • Juan Suero

    dude private PAAS is SOA ontop of private IAAS

    • http://www.janakiramm.net/ Jani

      Slightly disagree. Private PaaS is mostly managed by the vendors who
      provided it. It is far more easier to manage and maintain than IaaS.

  • Govind

    Honestly Jani – Private PaaS – when it becomes reality should abstract out PaaS itself. My application is there – manage provisioning/security/integration. There should not be need to learn PaaS concept at all.
    There is huge existing repository of applications and their hardware – if it can be utilized and managed – much better. BTW multi-tenancy is something one needs to think about with or without PaaS etc. It was there in ASP (no not microsoft asp) days and anybody who has created hosted platform knows about perils of too much abstraction..
    Private PaaS focus should be enabling existing apps to not worry about PaaS. If they do – they will face friction, because returns are too low. That is why it is restricted release to test the waters.
    One can always work with virtualization vendors to abstract out the metal/os and just run the app.
    Here too vendors who provide ability to run diverse set of applications/workloads will succeed the farthest.