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.

10 responses to “rPath’s Enterprise PaaS Is Not PaaS. Period.”

  1. Shawn Edmondson

    Hi Krish, looks like we miscommunicated on a few points.

    1. We are always careful to call this concept of platforms on demand “EPaaS” or “Enterprise PaaS,” not PaaS. It’s a new technical concept and term for a derivative of the common PaaS concept. And it is based on what large customers are telling us repeatedly. They want IT to offer, as a service, traditional OS/middleware platforms. They aren’t ready to switch to completely new platform abstractions like Heroku.

    While EPaaS isn’t a perfect term, it is an accurate description of the concept, and we received positive, welcoming feedback on it in dozens of face-to-face discussions at VMworld this week.

    2. Another point we always strive to make clear: rPath doesn’t offer an EPaaS solution (or any type of cloud). We are not a cloud vendor or MSP. Customers and partners combine our OS and middleware automation technology with third-party self-service automation and IaaS to create their own EPaaS platform-on-demand solutions.

    3. The focus of our briefing was not rPath’s products or even EPaaS for that matter. It was about the Enterprise Cloud Adoption Framework, the completely vendor-neutral adoption model we announced at VMworld and at cloudadoption.org. ECAF looks at common cloud patterns, including EPaaS as one instance, from both application and platform points of view. At our VMworld launch party and in many face-to-face discussions this week, response to ECAF was highly positive and engaging.

    Thanks again for your feedback on the terminology. I hope ECAF and EPaaS will become more clear and compelling to you over time.