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.
VMware’s latest effort, CloudFoundry, is not about VMware delving into the PaaS market even deeper. They have done that already with VMforce. CloudFoundry on the other hand is a fairly astute move to enable the development and rapid adoption of cloud based applications. The end goal is to sell what makes up a PaaS environment which is more enabling software. This would enable enterprises and businesses to move to the cloud. The problem with them moving now is that there are not that many applications that are cloud friendly. In effect more concentration on the application and less on the operating system which has always been VMware’s strategic direction.
PHP can run on the Azure Cloud. Microsoft has made this easier by sponsoring an Open Source SDK and Eclipse Plugin. It is not investing in Visual Studio for PHP.
VMware’s SpringSource acquisition will result in VMware directly implementing the SpringSource Java runtimes in a VMware Guest. VMware will also work to allow other open source application frameworks like Ruby on Rails, Python and PHP to run directly in VMware Guests. VMware will provide value added API’s to these run time frameworks, that will make deploying and managing applications built to these frameworks and run on VMware easier. This will put pressure on Microsoft to allow .Net to also run in this manner – potentially setting the stage for the dis-intermediation of Windows as an applications platform.