Articles in this series

LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

5 responses to “IBM PureApplication Systems: It Is Not PaaS. Period. But”

  1. What to Tell Your Boss If You Partied Too Much at IBM Impact | ServicesANGLE

    [...] Simplicity was the number one theme at this year’s show. Pure Application Systems, part of the PureSystems family, are a core part of IBM’strategy to use pattern technology to [...]

  2. Oracle PaaS Speculations

    [...] offering that fits the puritan description of PaaS or it is a cloud washed marketing strategy like IBM’s PaaS in a Box story. There are speculations that Oracle’s public PaaS offering (including their Database [...]

  3. June 20th – Annual Election and Speaker « GSLMUG

    [...] IBM PureApplication Systems: It Is Not PaaS. Period. But (cloudave.com) [...]

  4. Sherwood

    I found this is a very controversial topic as the author initially suggested. the logic behind the conclusion is “because the PureSystem supports legacy enterprise apps, and these legacy apps are not good candidate for PaaS, so PureSystem is not PaaS.”. This is like saying because I can hold a gun, I must be a criminal.

    We must recognize that there are many kind of enterprise “apps” out there and a big chunk of them are mission critical and care about transactional integrity, therefore they don’t lend themselves good candidate of the stateless, internet-scale architecture, e.g. bank’s core banking system (such as ATM) does not run on a Facebook like infrastructure, in other words, there is a big chunk of existing OLTP transactional workload that need PaaS services, and PureSystem tries to address tis type of workload first, then it can address further Cloud Centric workload as additional pattern.

    PaaS is a very broadly used term, it can be abused, if we go by Wikipedia’s PaaS definition, “Platform as a service (PaaS) is a category of cloud computing services that provide a computing platform and a solution stack as a service”. My understanding of the key value of PaaS is it abstracts the typical ISVs/developers need around development, deployment and life cycle management so that developers can create apps and monetize from the app quickly. It doesn’t sound right to judge an offering is PaaS or not based on the workload that “can” run on.