Skip to main content
Version: Current

Data Storage

In some cases, it is preferable to store the processed data continuously and work over the stored collection rather than sending all the data through queues. This is especially true for large batches of data and data with complicated downloads from a source or sources. If the process fails at some point, we can save ourselves from having to retrieve the data again.

This approach is much more efficient and cheaper for data transfers, but it is not always appropriate. We use Cursoring without output and send a message to other nodes in the topology with a reference to the collection only after the entire collection has been traversed.


The data collection is always only temporary. If we do not remove it, it is deleted automatically after 24 hours.


Data storage is managed by DataStorageManager. We get it from the container as follows:

await container.get<DataStorageManager>(CoreServices.DATA_STORAGE_MANAGER);

We identify the data collection using the id parameter and the optional app and user parameters, which can be used for more detailed data segmentation, e.g. during integration processes in multitenant environments.


We save the data using the store method:, [{ foo: 'bar' }, { john: 'doe' }], app, user);

Loading data

dataStorageManager.load(id, app, user);

Removing a collection

dataStorageManager.remove(id, app, user);