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.
Over the last few months we have identified a trend towards “diversity” in the PaaS provider marketplace. Platform as a Service has become Platforms as a Service, the providers are offering multiple choices at each layer of the platform infrastructure, and seeing their role as automating the provisioning of properly-configured instances as required at each layer of the stack.
On Aug 2nd, there was another entrant to this “diverse” PaaS provider marketplace called Cumulogic, a startup with a PaaS cloud positioned alongside Red Hat OpenShift and VMware CloudFoundry that we identified earlier.
As mentioned in a couple of recent posts, I have been building a prototype application using Open Source technologies that I plan to install on a number of available PaaS cloud platforms. The application is written in Groovy (with some bits in Java) and built on the Grails framework. This article is about my use of RedHat OpenShift PaaS and the controls available.
Over the last few months an additional subproject codenamed Quantum has emerged which deals explicitly with networking and has particpation from networking giants Intel and Cisco as well as from Citrix. It’s a mechanism for defining network topologies aimed at providing Layer-2 network connectivity for VM instances running in clouds based on the OpenStack cloud fabric. It is designed to be extensible to allow higher-level services (VPN, QoS, etc) to be built on top, and to cleanly handle the “edge of network” problem (i.e. the binding of the cloud into the internet).
Red Hat’s Cloud is to play at all levels in the stack, from IaaS and PaaS through to hypervisor and of course operating system. Each layer is comparable to offerings from competitors.except for MRG – Messaging Realtime and Grid, of which version 2.0 has just been released.
As mentioned in my previous piece I’ve been doing some prototyping using SpringSource’s Grails. Grails can be thought of as the top of the stack. If you pick up Grails you would naturally pull in the other pieces of SpringSource, including vFabric and ultimately vFoundry. In a future post I will deal with what happens when you stick Grails onto vFoundry, but at this stage I’ve been assessing the health of the SpringSource Ecosystem.