History application

Background

The engine application persists every protocol state change along with the action which triggered the change, thus ensuring a strong audit trail and traceability by design.

The engine does not require these historical data, however, so they can be moved to a separate data store in order to mitigate issues caused by ever-increasing data volumes.

History application is a companion application to the engine application. It is responsible for transferring historical data from the engine's store to the history's data store.

Further links

The history application's APIs are documented here.

Read further details about different setup scenarios and configuration options.