Cloud Foundry stages a comeback

Practically no developers in their right mind want to write an application from scratch and run it on single server anymore. Instead, they want to tap existing services, keep the original coding to a minimum, and test/deploy the finished application in as automated a fashion as possible on scalable infrastructure.

At the start of the cloud era, PaaS (platform as a service) was intended to handle that process, much as the application server handled it in the client/server era. But a funny thing happened: PaaS never really took off. People opted for home-built solutions, with their own scripts and sets of services, and when Docker came along they began figuring ways to dev and test using Linux containers and various container management solutions.

But all that is pretty complicated to set up yourself, which may be one reason why PaaS seems to be making a comeback. From the start the two big PaaS plays have been Cloud Foundry and OpenShift — and they still are (though you can now add Microsoft Azure Service Fabric to the mix). All three now support Docker containers and adhere to the standardized container format developed by the Open Container Initiative.

An open source project with its own foundation, Cloud Foundry is arguably the leading PaaS — though as I discovered in an InfoWorld interview last week, Cloud Foundry Foundation CEO Sam Ramji dislikes the PaaS moniker. “I’m not going to use the PaaS word because it has a historical and failed market,” he says. “[It was] slapped on by analysts who didn’t have anything better to call it and it came out of the NIST definition of cloud computing [PDF]. It’s not a very good definition. It’s very foggy and it’s constraining.“