Entries in OpenPaaS (1)


OpenPaaS & VMforce ... some insights

After following the tweet'd conversation between James Watters (@wattersjames) of VMware and James Urquhart (@jamesurquhart) of Cisco and CNET, I tossed in the thought that polyglot persistence was implied as a major aspect of VMware's Open PaaS strategy. The strategy was discussed last spring by Steve Herrod in the context of VMware's acquisition of SpringSource and the rapid rollout of VMForce.com, the impressive joint effort of Salesforce.com and VMware.

Dave McCrory has recently provided excellent insights about OpenPaas in a series of posts this month, the most relevant to the polyglot persistence notion being this one.


In this diagram (above), there are two URLs each providing access to an Application. The first application on the left has a single Application Instance and that App Instance is bound (see Binding Labels) to a MySQL Instance (Service Instance) and a RabbitMQ Instance (Service Instance). The two Service Instances are created from the Service Catalog’s MySQL and RabbitMQ entries.

The second Application has three App Instances inside of it, all of which are bound to the SAME RabbitMQ Instance that the first Application is (this means that the two Applications can share information through the RabbitMQ Instance). The MySQL Instance is a separate MySQL Instance from the first Application MySQL Instance, although both are based/invoked from the MySQL Service in the Service Catalog. The Redis, Memcache, and MongoDB instances are all bound to each of the App Instances in the second application and are used by all three instances.

[My thanks and a hat-tip to Tim Freeman (@peakscale) for pointing this point out to me.]