Leading technology vendors have come together to develop a standard for Platform-as-a-Service (PaaS) solutions to allow easy management and migration of applications across public and private clouds. Cloud Application Management for Platforms (CAMP), a PaaS management Application Programming Interface (API) specification, has been submitted to the Organization for the Advancement of Structured Information Standards (OASIS) to serve as a standard for all PaaS providers.
A range of PaaS solutions such as Microsoft Azure, Amazon’s EC2, and others are available in the market and are prolifically used across enterprises. Each solution offers its own web console for application deployment and management, making the migration of workloads from one cloud service to another a huge and tedious task. This factor is a deterrent to the growth of PaaS.
Vendors including Oracle, RedHat, Rackspace, Huawei, Software AG, CloudBees and Cloudsoft pooled development efforts to form CAMP, an API with a set of commands for managing workloads. The goal is to get all PaaS vendors to implement CAMP in their solutions to help customers. Third party software providers too can build tools to make application management easier and independent of platform, language or framework with CAMP.
Why should you implement CAMP?
The CAMP API offers many advantages for PaaS consumers and providers.
For consumers, “portability between clouds” will no longer be a decision driving factor in choosing a PaaS solution. With the standardization of deploying, stopping, starting, uploading, configuring, and updating applications, consumers can evaluate solutions based on their advanced features and services. In time, CAMP could be incorporated into application development environments (ADEs) and application management systems as a plugin which will help drive the quality of the standard.
For providers, CAMP addresses one of the chief complaints of consumers in the PaaS space. In addition, a common management API allows providers to leverage the experience and insight of the specification’s contributors and invest their design resources in other, more valuable areas.
Going forward, CAMP could include more features such as supporting workload migration. It includes well planned extensibility points to accommodate future evolution.
The development of CAMP is a great step forward for the PaaS market that should drive further adoption. Contributing companies in CAMP evolution plan to incorporate support for it in their own products, as appropriate.
Learn more about CAMP here.