ActiveState Stackato and CumuLogic are private PaaS. Over the last few weeks Stackato has moved to a 2.0 version and CumuLogic has moved out of Beta to a 1.0 release. CumuLogic 1.0 is a Java-only PaaS with support for Amazon, HP Cloud Services, and private clouds including Citrix CloudStack, Eucalyptus, OpenStack and VMware vSphere. Stackato has a similar range of public and privae IaaS on which it operates (vSphere, KVM, XenServer, OpenStack, EC2 AMI, HP CS) but it has a much broader set of language compatibilities including .NET.ther new features in Version 2.0 are a centralized web-based management console and some support for charge-back (i.e. billing) through API. Performace management is through integration with New Relic. There is additional security support in multi-tenancy by using Linux Containers (LXC).
We asked OpenStack recently whether they were going to do PaaS, they said that this was happening in the community around them, and today we have an announcement of one way of doing it: with VMware’s Open Source CloudFoundry.
ActiveState has created a Private PaaS that supports Perl and Python as well as Java, and is based on the Open Source CloudFoundry distribution, packaged and distributed in a VM image, or installed to a wide range of IaaS platforms (public or private).
ActiveState is well known in Open Source communities as packaging/distribution vendor for dynamic languages – Perl, Python and Tcl. A sort of Red Hat for dynamic development languages. It also has a Komodo IDE for these languages, and a strong pedigree in contributing back into the Open Source projects which it packages. Stackato is also essentially a packaging of these and other Open Source technologies. It’s an interesting take on the PaaS space – PaaS becomes a packaging problem – just like the Linux Distro. For the customer, the choice of PaaS/Distro is partly about the breadth in the package and partly the mix of pricing, support and warranty offered by the PaaS/Distro.
To recap the story so far, I’m prototyping an application and deploying it to various PAAS environments. I am not getting any special help from any of the vendors in this exercise – you can think of me as a “secret shopper” for PaaS, although I don’t hide my identity. I am approaching each platform on its own merits, and in these posts I am recounting and contrasting my experiences and reaching some general conclusions about the PaaS market.
The announcement of CloudFoundry means the public declaration of full on war between VMware, and the two traditional OS vendors, Microsoft and Red Hat. Both traditional (not quite legacy yet) OS vendors are going to have to rapidly bolster their own PaaS cloud offerings. This will be a particular challenge for Microsoft as Microsoft has always gravitated strongly towards having a tightly integrated stack of software, and not being very open to open source frameworks like Spring, Ruby, and PHP.
Over the last few weeks, VMware (as we indicated in an earlier post) and Red Hat have initiated two very similar initiatives known respectively as CloudFoundry and OpenShift. These are Platform as a Service (PaaS) plays, being developed for the longer term, primarily looking to encourage the development of (and thereafter to provide infrastructure for) applications specificallysuited to the the cloud. In this article we compare and contrast the two offerings and discuss their significance for the PaaS market as a whole.