Event catalog
Define what each event actually means.
Start with a question ↗Capabilities
Event-driven workflows, with a clear point of view.
Make event-driven work visible from trigger to consequence. Event Stream connects event meaning, consumer expectations and replay decisions so teams can reason about asynchronous behavior.
Capabilities
Event-driven workflows, in focus.
Consumer map
See which workflows depend on it.
Start with a question ↗Replay notes
Document when reprocessing is appropriate.
Start with a question ↗A closer look
Define an event precisely
Events describe something that happened. Keep that distinction clear so consumers do not mistake an event notification for a command that can be applied without context.
Continue with the practical guide ↗Event Stream
Discuss your workflow.
Write with a little context about event-driven workflows and the question you would like to explore.
contact@event-stream.lizh.cloud