Several CoreMedia core features like My Edited Content and Workflow Lists (backed by 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.

Deprecation Notice

The in-memory replacement is deprecated. It is recommended to use the SQL replacement instead. See Section 4.2.4, “SQL Replacement for MongoDB-Based Editorial Services”.

Limitations

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

Besides not supporting CoreMedia 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.

In the following, you find how to activate the in-memory persistence for Studio Server and Workflow Server.