You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to understand the behavior of an application, it is very helpful to be able to analyze, which changes to the system lead to the current (or past) state of some entities.
Especially event sourcing architectures promise to improve the traceability of a system, because every state-change is triggered by commands and/or events received by the application. The purpose of this epic is to take the first step by introducing a message history having the following features:
Add a REDIS implementation of the MessageStore interface acting as a time-series database for messages.
Adding the capability to view the messages for a given message key that where received by a single MessageLogReceiver.
Determining the delta between the payload of any two messages for a given message key
The text was updated successfully, but these errors were encountered:
In order to understand the behavior of an application, it is very helpful to be able to analyze, which changes to the system lead to the current (or past) state of some entities.
Especially event sourcing architectures promise to improve the traceability of a system, because every state-change is triggered by commands and/or events received by the application. The purpose of this epic is to take the first step by introducing a message history having the following features:
The text was updated successfully, but these errors were encountered: