muoncore / stack-event Goto Github PK

Allow building relationships between events.

When scaling a system, it is unlikely you will remain with a single event infrastructure.
Instead, you will likely want to persist some events into a "local" event store, and others into one for inter service comms. (E.g. the difference between aggregate root internal events and external domain events).

This requires being able to specify, by name or tag, the event store to use on emit and replay.

Need to know when the hot/ cold switch occurs

Muon Version: All
Language: jvm

MIgrated from muoncore/muon-java#44
Can access subscription and metadata about the stream if constructed and used.

Idea is to enable richer control and notifications about the replay status. Eg, know when we cross between cold and hot replay. Requires updating the replay to have a dedicated protocol, not piggy back the RS one.

Support the reconstruction of related events based on entity ids.