Blog

I’ve been asking myself a question lately: is Platform-as-a-Service a disruptive technology? I’m not talking about whether PaaS will change things or is really different – it’s obvious that it has the potential to make a big difference. I’m talking about disruptive in the sense that Clayton Christensen introduced – the definition on Wikipedia is “an innovation that creates a new market by applying a different set of values, which ultimately (and unexpectedly) overtakes an existing market”.

This is an important question. If PaaS is a ‘sustaining’ innovation then we can expect a fairly smooth transition from the use of Infrastructure-as-a-Service through to Platform-as-a-Service. Existing companies in the IaaS area will be incentivized to invest heavily in PaaS and will start making money right away, probably from the IT departments in large companies.

But if PaaS is disruptive, that means that it will start out not meeting the minimum requirements for the mainstream market, making sales to mainstream customers (read corporate IT departments) difficult. At Appsecute we’ve experienced ourselves the benefits of PaaS – the potential is there to vastly reduce the costs and time involved in operating production systems. But if PaaS is missing key capabilities then corporate IT simply can’t buy it, no matter what the potential cost savings and benefits in agility. They have to stick with IaaS, with its greater maturity of tools and greater amount of control over the technology stack.

Disruptive technologies first find a foothold in another, non-mainstream market that has a different set of criteria for success. Typically disruptive technologies look terrible when evaluated against mainstream criteria, right up until they don’t. So disruptive technologies are consigned to marginal or niche markets where they gradually increase their capabilities, until one day, suddenly, they do have enough capability to be used in mainstream markets, and still have their unique benefits. Their traditional technology competitors are typically far ahead in capability by this time, but suddenly the disruptive technology is good enough on the mainstream criteria, and offers some other compelling advantage (cost savings, or some unique advantage) and all of a sudden the mainstream market flips, ditches the existing technology and adopts the disruptive technology en masse.

So let’s look at PaaS. Right now it’s missing some things that IT really need for production applications. Compliance with industry regulation, security standards, audit standards, repeatable and rigorous deployment processes – most of these things are missing from PaaS right now. I would go so far as to say that PaaS isn’t usable for production corporate applications.

But PaaS is finding a home in niche markets. It’s being used for development and test environments in corporates. And it is being used by the devops movement to run production applications outside of the control of IT. In these environments it doesn’t matter that PaaS isn’t ready to meet mainstream IT requirements yet.

PaaS is increasing in capability every day. At Appsecute we deal closely with Cloud Foundry from VMware, and the pace of innovation in the Cloud Foundry community is astonishing. And one day it will have enough features to be used for mainstream production applications. At Appsecute we’re doing our bit to help it along, by adding some of those features via our management tools.

I don’t know if PaaS really is a disruptive innovation, but I’m seeing a few signs that it is. And if that’s true then we are likely to suddenly see a transition from PaaS as a tool for devops to PaaS as a mainstream environment.

If PaaS is disruptive then at some stage in the near future we will see explosive adoption, replacing the use of Infrastructure-as-a-Service. It won’t be linear, it will be exponential.

If PaaS is disruptive then it’s going to be an interesting future for the cloud.

6 thoughts on “Is PaaS a Disruptive Technology?

  1. Nice write up Mark,

    I think one of the questions is that needs asking is who is PaaS disruptive too?
    For instance, if the PaaS provider bundles compute resources (which it does by default) then its actually disruptive to IaaS and on premise.
    Is PaaS is a disruption to the software development eccosystem. Must be because its different way of doing it at a much lower cost, as you say it appeals to current non customers, but it does appeal.

    What would be really interesting, would be if an organisation outside the mainstream created an offer/service using PaaS and took it to an incumbent. Hypothetical example, A bank creating a payroll / accounting service and selling it directly to end clients leveraging PaaS…you see that you have a disruptive technology.

  2. I find PaaS+IaaS+SaaS more interesting to consider than PaaS by itself. Especially when IaaS = higher-order services like AWS’ SNS, SQS, etc. Or vertical market clouds like FinQloud. Seems to me that the combo of the three XaaS levels could enable rapid development and efficient operation of applications that collect the aforementioned “missing pieces” from external providers.

  3. Hi Jeff and Paul,

    We are talking a slightly broader view of PaaS, certainly in the longer term. In the Cloud Foundry model (which is by default the Appsecute model right now) applications can be bound to instances of services.

    Services at the IaaS layer like storage, databases, message queues etc can be exposed to the PaaS layer by being wrapped up as PaaS ‘services’ to be bound to applications.

    I can see the same thing happening for SaaS offerings, especially those that provide an API (thinking of logging, billing services, sending email and a bunch of others). By providing a PaaS service wrapper for these they can also be bound to PaaS applications.

    So I agree that the combination of PaaS + IaaS + SaaS is more interesting, but at least for application development and deployment I can see it all being folded into PaaS from the point of view of application developers and operations. (For example we use RabbitMQ, MySQL and a bit of Amazon S3 within Appsecute).

    And as soon as IaaS is bundled into PaaS, the PaaS providers can increase their efficiency/profit by sourcing these IaaS services internally rather than through external vendors. For example, we use Tier 3′s Web fabric for running the Appsecute site, and they have their own data centers rather than using an external IaaS provider. So if their PaaS business takes off they are taking business off of IaaS (e.g Amazon) rather than it being a PaaS + IaaS combination – starts to look disruptive to IaaS.

  4. Pingback: The 20 Year Enterprise Innovation Cycle–Defrag Session (Plus Free Passes!) | The Diversity Blog - SaaS, Cloud & Business Strategy

  5. Pingback: The 20 Year Enterprise Innovation Cycle–Defrag Session (Plus Free Passes!)

  6. Pingback: The 20 Year Enterprise Innovation Cycle–Defrag Session (Plus Free Passes!) | Padroni.net

Leave a Reply

required
required, will not be published
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>