IaaS eats PaaS’ lunch, and long live both

IaaS (Infrastructure as a Service) and PaaS (Platform as a Service) are often described as competing paradigms for the future of the cloud.

A commonly heard view is “PaaS is the future of cloud services and IaaS will slowly go into the background”.

Here is a contrary view.

First lets name some vendors: Microsoft’s Azure is seen as a .NET PaaS, and Google’s App Engine is seen as a Python&Java PaaS; while Amazon’s AWS and Rackspace’s Cloud are seen as IaaS plays.

The real world is of course more interesting then that. IaaS platforms do offer PaaS solutions through their eco-system: Heroku (on AWS) is often mentioned; and Windows servers on AWS can of course run .NET…

Conversely, PaaS providers are bringing out IaaS-like features: Microsft Azure recently brought out the ability to create images of servers (IaaS has had this feature for some time) and has long offered “Azure Blobs” as a competitor to AWS S3; Google recently added “Google Storage” and is rumored to be cooking an EC2 competitor.

More fundamentally, it is a fact that the IaaS approach has attracted many new adopters to the market. One reason is: the nuts-and-bolts approach of IaaS makes it easy (or easier) to port existing applications to the cloud, quickly.

This benefit is not going away, any time soon. It may well be the reason Microsoft and Google are adding IaaS-like features.

What will the future bring? Gazing in our crystal ball, we see the clouds becoming brighter 😉

Most major vendors will offer a layered stack: a lower IaaS layer directly exposed through Web Service APIs, and a PaaS layer running on top of the IaaS layer.

The PaaS layer will expose one or more programming models (Ruby, Python, Java, .NET, …) along with a Web Service API. Developers will be able to choose their “favorite PaaS” out of several on their chosen IaaS, and get a well defined programming model and a well defined set of APIs for that specific PaaS.

So IaaS “wins” in the sense that it is a required offering for all major vendors; while PaaS “wins” in the sense that it makes life easier for the developer. The developer will go to PaaS for speed of getting results, and to IaaS when she needs the nuts-and-bolts of the cloud.

IaaS will “go into the background” about as much as the Linux or Windows OS-s have “gone into the background” in the past 10 years… In fact they have done just that, but it hasn’t hurt them one bit.


  1. infrastructure as a service says:

    yes, the statement is true , eating means taking both benefits from each other. from SaaS, now the industry is moving towards platform as a Service (PaaS). PaaS offers a development platform for developers. The end users write their own code and the PaaS provider uploads that code and presents it on the web. SalesForce.com’s Force.com is an example of PaaS. PaaS provides services to develop, test, deploy, host and maintain applications in the same integrated development environment. It also provides some level of support for the creation of applications. Thus PaaS offers a faster more cost effective model for application development and delivery. The PaaS provider manages upgrades, patches and other routine system maintenance. PaaS is based on a metering or subscription model so users only pay for what they use. Users take what they need without worrying about the complexity behind the scenes.

  2. Velvel swapnel says:

    I don’t see any points about why this is a contrarian view – Other than saying that PaaS vendors are offering IaaS. What is your point.

    • The point is that far from disappearing into the background, IaaS is showing the strength of an “operating system” for the cloud. It is an essential offering – the PaaS vendors cannot ignore it and are trying to compete by expanding their offering to include IaaS.


  1. […] This post was mentioned on Twitter by Stuart Coulson, Porticor cloud sec. Porticor cloud sec said: IaaS eats PaaS’ lunch, and long live both http://goo.gl/fb/8Hcuf @porticor […]

Speak Your Mind