Expand description
Client Event Log
The goal here is to maintain a single, ordered, append only log of all important client-side events: low or high level, and move as much of coordination between different parts of the system in a natural and decomposed way.
Any event log “follower” can just keep going through all events and react to ones it is interested in (and understands), potentially emitting events of its own, and atomically updating persisted event log position (“cursor”) of events that were already processed.
Structs§
- Event
Kind - Event
LogEntry - Event
LogId - Ordered, contiguous ID space, which is easy for event log followers to track.
- Event
LogId Prefix - Event
LogId Prefix All - Unorded
Event LogId - A self-allocated ID that is mostly ordered
- Unordered
Event LogEntry - Unordered
Event LogId Prefix All