-
Notifications
You must be signed in to change notification settings - Fork 105
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
Clarify ordering guarantees out externalized events #415
Comments
From what I see there is out of order processing at least for internal events, I have a proof right here:
so as you can see "FINISHED" arrives sometimes before it is really finished. It makes sense as this is @ApplicationModuleListener with Async annotation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I am trying to understand the ordering guarantees of externalized events, in particular whether it is guaranteed that two events originating from two concurrent requests are sent to Kafka (or whatever message broker is used) in the exact same order as the database transactions are committed? This is vital for ensuring a consistent state across the database and the Kafka event consumers. Are the transaction listeners used for sending the message somehow synchronized? Thanks for any clarifications!
The text was updated successfully, but these errors were encountered: