Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dealing with missed events #55

Closed
nanov opened this issue Jul 14, 2017 · 6 comments
Closed

Dealing with missed events #55

nanov opened this issue Jul 14, 2017 · 6 comments

Comments

@nanov
Copy link
Contributor

nanov commented Jul 14, 2017

What is the recommended way to deal with missed events?
I tried doing an RPC queue requesting those ( aggId, guardedRev, aggregateRev ) and the handling those one by one, but this approach seems to bring some problems with it ( mainly because of the handle inside handle ). Should i just send the missing events again thought the normal events queue ( send/receiver ) ?

@adrai
Copy link
Contributor

adrai commented Jul 14, 2017

@nanov
Copy link
Contributor Author

nanov commented Jul 17, 2017

Well, I had already read those issues and proceeded in a similar manner.
Actually my "problem" is simpler then i thought, what should be requested from the EventStore is guardedRevision-1 and aggregateRevision-1 from the info object.
Then I process those one by one with the normal handle method ( as I make use of event extenders and preExtenders ), when done in this way everything seems to work as expected.

Is there any particular reason to call only the viewbuilders when replaying events? I am asking because I am thinking about adding it as an option.

@adrai
Copy link
Contributor

adrai commented Jul 17, 2017

Short answer:
When replaying, only the readmodel should be rebuild...
I.e. If you call another service during evtExtenders this should not be called again when rebuilding... -> you can't force everyone to handle rebuilts...

@nanov
Copy link
Contributor Author

nanov commented Jul 17, 2017

I see, it does makes sense, what about adding an option to the (pre)event extender to be replied?

@adrai
Copy link
Contributor

adrai commented Jul 17, 2017

@nanov
Copy link
Contributor Author

nanov commented Jul 17, 2017

My bad, it absolutely does!

@nanov nanov closed this as completed Aug 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants