The OASIS international consortium has launched the Cloud Application Management for Platforms (CAMP) Technical Committee, a project to define the interoperability standard for managing applications in Platform as a Service (PaaS) environments.
CAMP will leverage similarities between commercial and open-source PaaS products to produce a simple API that is language-, framework-, and platform-agnostic.
Using CAMP, companies will be able to migrate their cloud applications from one PaaS vendor to another by mapping the requirements of applications to the specific capabilities of the underlying platform.
“Companies are starting to experiment with PaaS, but even as they do, it becomes clear that variations between the vendors’ application interfaces will make it hard to move applications from platform to platform. That looks a lot like vendor lock-in, and it’s putting customers off,” said Rachel Chalmers, VP of Research at The 451 Group. “It is encouraging to see that this issue has been grasped by the vendor community and is being addressed within the OASIS framework.”
“CAMP’s goal is to define a simple standard RESTful API along with a JSON based protocol, with an extensibility framework that enables interoperability across multiple vendors’ offerings. Using CAMP, users can manage their application lifecycles and move applications between clouds easily,” said Martin Chapman of Oracle, chair of the OASIS CAMP Technical Committee. “We expect CAMP to foster an ecosystem of common tools, plugins, libraries and frameworks, which will allow vendors to offer greater value-add.”
Work on CAMP was initiated in late 2010 by a group of seven companies, Oracle, Red Hat, Rackspace, Cloudsoft, Huawei, CloudBees, and Software AG. They transitioned the project to OASIS in order to ensure CAMP would benefit from broad industry participation in an open, collaborative setting.
“CAMP is one of several new Cloud standardization projects at OASIS that make use of JSON and REST,” noted Laurent Liscia, OASIS executive director and CEO. “We see the standardization of CAMP as an important step in guiding the industry into an ecosystem of interoperable and portable cloud systems.”
The CAMP Technical Committee is open to all interested parties, and new members are encouraged to join at any time.
Archives of the work are accessible to both members and non-members, and OASIS invites public review and comment on the work.
Hot Topic
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...