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. Continue reading VMware’s CloudFoundry and Red Hat’s OpenShift – Compare and Contrast
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. Continue reading CloudFoundry Apps not VMs
As mentioned in a previous post I’ve been at EclipseCon (the annual conference for the Eclipse Open Source Development tool platform, where the Open Source community gathered to discuss how to build the tooling that will allow us to build and target applications directly at the cloud, without concern for the underlying infrastructure.
The key issue is interoperability – are we building applications for The cloud, or for A cloud? For application servers (or indeed .NET) as discussed in our previous piece, the application level APIs need not significantly change, the set of services provided by the application server is transparently provided in the cloud. Applications written in languages such as PHP that hitherto had run in a web server directly against the operating system (rather than in a container) could be extended to access services inside the Application Server or the .NET framework.
However, since there is a broad consensus about the cloud architecture, interoperability for languages like PHP can be achieved through a fairly simple set of APIs that would allow applications to access scalable storage (as BLOB, REST or Queue), and to deploy/provision applications. Continue reading Developing PHP on Microsoft Azure
During his technical keynote at VMworld, Stephen Herrod added a fourth leg to the now familiar previous three legs of the VMware strategy. The previous three were View (Desktop), vSphere (the data center), and vCloud (the internal and external clouds). The new addition was the elevation of vApps to a fourth leg in the stool which describes the VMware strategy. This fourth leg of the stool is all about VMware as an application platform, and VMware adding value directly to how applications run. This new fourth leg ultimately results in a new strategy from VMware allowing applications platforms (and therefore applications) to be run directly in a VMware Guest without the need for an underlying Windows or Linux operating system. Continue reading VMware’s “No OS” Application Platform Strategy