Configuring MongoDb Service Registry

This configuration represents a sample of how CAS service registry may use MongoDb as the underlying persistence mechanism for services. The configuration requires that a userid with read/write access to the database be specified. The code was tested against a sample repository on www.mongohq.com.

Why would I want this?

You might not. Consider the increasingly popular JSON-file-backed service registry instead.

This MongoDB solution has some advantages over the current JSON-file-backed solution. This MongoDB solution is read-write, enabling fuller use of the CAS service registry management administrative UI web application and is transactional, while lower-ceremony and "lighter" than dealing with a traditional RDBMS.

Alternatively, you may want to consider using ReadWriteJsonServiceRegistryDao.