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.
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.
It is interesting to see Edward’s comment that according to EMC/VMware, widespread production deployment of Cloud Apps is 3-5 years off. If that is the case the VMware CloudFoundry initiative should be focused on cutting-edge development rather than porting existing apps, and in much the same way that Microsoft has always courted developers, CloudFoundry should be the latest cool thing for developer productivity. It’s interesting to talk about this stuff in the abstract, and at the strategic level, but sometimes it’s worth understanding what happens when you need to make the decisions for yourself.
VMworld is clearly the largest dedicated virtualization conference, and yet from an Open Source perspective it is slightly disappointing because the VMware ecosystem naturally attracts proprietary software vendors, and also some of the more interesting activities in Open Source are through multi-vendor foundations which do not have the same marketing budgets as vendors themselves.
Nevertheless, there are a number of key Open Source players, and some interesting smaller players, represented at VMworld.