loading table of contents...

3.3.6. In-Memory Replacement for MongoDB-Based Services

Several CoreMedia core features like CapLists, notifications and projects/to-dos use MongoDB as a persistence layer. Although not recommended it is possible to substitute MongoDB with an in-memory persistence layer.

[Note]Note

There is no in-memory replacement for the persistence layer of the Elastic Social extension. MongoDB is required for that.

Besides not supporting Elastic Social there are other functional limitations to the in-memory approach. Collaboration based on projects/to-dos will not work properly with more than one Studio server.

[Note]Note

In order to activate the in-memory persistence for Studio and the Workflow server, update Blueprint extensions, using the Maven profile controlroom-memory. It will add all necessary Maven dependencies to Studio and Workflow Server, in order to persist Control Room data in-memory. For more information how to update Blueprint extensions, see Section 4.3.2.1, “Adding, Disabling or Removing an Extension” 

      mvn com.coremedia.maven:\
      coremedia-blueprint-maven-plugin:\
      update-extensions -Pcontrolroom-memory
Prev Up Next
 Home