You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A better solution would be to keep track of streams the client has seen and a rough estimate of the event number I'm expecting then do a delay only if I detect an out of order event and only for the duration it takes for the next event to come.
We'll have to insert some clever algorithm tricks like bloom filters. Won't need to be 100% certain but 99.99 at least
The text was updated successfully, but these errors were encountered:
Currently to overcome the event ordering issue I put a 2 second delay between receiving events from ES and processing the event. As explained here: https://github.com/volak/Aggregates.NET/blob/master/src/Aggregates.NET.Consumer/Internal/EventSubscriber.cs#L368
A better solution would be to keep track of streams the client has seen and a rough estimate of the event number I'm expecting then do a delay only if I detect an out of order event and only for the duration it takes for the next event to come.
We'll have to insert some clever algorithm tricks like bloom filters. Won't need to be 100% certain but 99.99 at least
The text was updated successfully, but these errors were encountered: