search

MerrionComputing / EventsSourcing-on-Azure-Functions

A library to demonstrate doing Event Sourcing as a data persistence mechanism for Azure Functions
MIT License
103 stars 20 forks source link

Add "Causation identifier" #9

Closed MerrionComputing closed 4 years ago

MerrionComputing commented 4 years ago

The event wrapper should have a field for a causation identifier (not mandatory) which can be used to store the identifier of what caused the event to be written.

This is most likely to be a command unique identifier but could also be a notification unique identifier if the system is set up such that events can trigger events. (I'm not convinced this latter is a good design but am not going to pre-emptively eliminate it as a possibility)

MerrionComputing commented 4 years ago

Done in latest commit