A persistence agnostic Event Store for .NET
MIT License
Bot releases are visible (Hide)
Maintenance release
Updated Target Frameworks:
Published by AGiorgetti almost 3 years ago
Published by AGiorgetti over 3 years ago
Published by damianh over 10 years ago
Polling Client
As an alternative to the dispatcher mechanism and improved replay / catch-up story we have implemented a CheckpointNumber in the stores that guarantees ordering across the streams. This number is guaranteed to increment but not guaranteed to be sequential. This allows you to get all Commits from a specific checkpoint and observe new ones. This implementation is polling based (and thus works for all engines) so it doesn't have the same low-latency attributes of the dispatcher mechanism. You can see how to use it here: https://gist.github.com/damianh/6370328 .In this, instead of the store tracking what has been dispatched, the onus is on the client to track what it has seen. And upon restart, start subscribing from what it last saw.
In the future I'd like to see / implement reactive clients that leverage stores that are observable.