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.

3 responses to “CAMP: Will It Be Relevant?”

  1. Tobias Kunze

    Thanks for this thoughtful writeup. While I agree with many of your observations, I wouldn’t arrive at the same conclusions. Not because I happen to be one of the authors, but because I believe there may be two misunderstandings that are worth pointing out. First, CAMP makes no assumptions as to what type of application a particular PaaS supports, be it “distributed” or “legacy”. It merely operates on “Assemblies” and their constituent “Components”. Second, the set of CAMP operations has been designed to be as basic as possible so as to expressly not impede innovation in the PaaS itself. As a result, it seeks to standardize only uncontroversial operations such as importing application artefacts, discovering assemblies, or monitoring components.