NephoScale became the latest IaaS vendor to use Cloud Foundry as the basis for a Platform as a Service offering by announcing the Beta release of CloudPaaS, today. CloudPaaS supports Ruby, Python, PHP and Java/Spring in addition to database services that include MySQL. CloudPaaS allows NephoScale customers to take advantage of preconfigured application stacks for development without the challenges of provisioning and configuring infrastructure prior to deploying a platform for application development. Like many IaaS-PaaS bundles, CloudPaaS intends to entice customers to take advantage of the company’s NephOS IaaS platform as customers become familiar with its platform and customer service.
James Watters, Head of Cloud Foundry Product, Marketing and Ecosystem at Pivotal, remarked on the significance of NephoScale’s selection of Cloud Foundry version 2 as the basis for CloudPaaS as follows:
Hosting providers are increasingly adopting Platform as a Service in response to developer demand. Cloud Foundry dramatically lowers the barrier for ecosystem participation in the PaaS market to meet the growing demand from developers. NephoScale’s decision to leverage Cloud Foundry supports our vision to deliver a platform that significantly reduces development cycles and accelerates time to market for developers and cloud operators alike. Enterprises seeking to leverage Cloud Foundry can now consider NephoScale for both public and private deployments.
Here, Watters elaborates on how Cloud Foundry “lowers the barrier for ecosystem participation in the PaaS market” in a way that renders it increasingly difficult for specialized PaaS vendors to compete against a commercialized PaaS offering based on Cloud Foundry. Bolstered by partnerships with IBM, Piston Cloud and VMware, Cloud Foundry’s rise in the PaaS space has been remarkable in recent months, particularly given news of its integration with OpenStack and the associated announcement that Piston’s Joshua McKenty would join its advisory board. The key question for the PaaS space now is whether private, proprietary PaaS vendors will be able to gain traction or whether Cloud Foundry-based PaaS platforms will become the de facto standard given the promise of their interoperability with other Cloud Foundry-based products and integration with OpenStack.