Blueprint Developer Manual / Version 2506.0
Table Of ContentsSeveral CoreMedia core features like My Edited Content and Workflow Lists (backed by CapLists), Notifications, and Projects/To-Dos use MongoDB as a persistence layer. It is possible to substitute MongoDB with an SQL persistence layer.
Recommended: SQL Persistence
It is recommended to use the SQL persistence layer instead of MongoDB. Currently, MongoDB is still used by default, but this will change in a future release. Further, the possibility to use MongoDB for the features listed above will be removed completely in a future release.
Note that switching to the SQL persistence layer in an existing installation requires migrating your data from MongoDB to SQL if you have used the features listed above and want to retain their data.
Features Requiring MongoDB
There is no SQL replacement for the persistence layers of the extensions Elastic Social and Analytics Connectors. MongoDB is required for that.
For a system to run without MongoDB, the extensions must be removed from Blueprint as described in these sections:
The following sections describe how to enable the SQL persistence layer for all supported features, and how to migrate their data from Elastic Core to SQL persistence:
The following sections describe how to enable the SQL persistence layer and migrate data for every supported feature separately and in greater detail:
