VMware is not a household PaaS name (are there any?) but vFabric will take it there.
As a CEAP, vFabric provides a variety of vetted components – Spring for AD, GemFire for XTP, Rabbit for messaging, etc. Of course the underlying lingua franca is Java, a language ubiquitous in the enterprise. Interested cloud platform providers, such as carriers – will no doubt take a close look at the vFabric offering as a basis for PaaS competitiveness.
The other story is one that I’ve been following for a while – the potential shakeout in PaaS. I pointed out last year that the SpringSource acquisition put VMware in position to dictate some terms in the cloud application platform space. Not everyone believed, but here we are with VMware moving up the stack (albeit not with CloudFoundry, but hey, nobody’s perfect).
The next question – how far can VMware go in its “encirclement of Microsoft” strategy? VMforce and Google App Engine for Business are a great start, but the PaaS shakeout is just getting started. Smaller providers must catch Maritz mania for the VMware strategy to be fully realized.
It will be interesting to see how things play out. For now I plan to enjoy the next couple of days of VMworld and report back.
Note to Microsoft: Eclipse is an IDE not a language.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
The Mobile Scenario: Taking Mobility to the Next Level
The definition of "mobile" in the post-app era will involve new interactions such as bots and conversations, new devices such as wearables...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.