Command dispatch with strong consistency guarantee #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for command dispatch that waits for all strongly consistent handlers (event handlers, process managers) to have successfully processed all events created by the command being dispatched.
Implementation
Created a
Subscriptions
module to track all event store subscriptions. It uses an ETS table to track subscriptions and streams/versions that have been handled per subscription.Added a
consistency
option to event handlers, process managers, and command router. It supports either:eventual
(default) or:strong
consistency.Consistency is guaranteed by a new command dispatch middleware that blocks after successful dispatch. Once you receive an
:ok
reply from a command dispatch you are guaranteed that the handlers have completed.Fixes #82.