DP-396: MQ Outbox Pattern - Publisher #493
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jakzal
force-pushed
the
feature/DP-396-message-outbox-publisher
branch
from
37b34c3 to
83c18ae
Compare
dharmverma
approved these changes
Aug 24, 2024
dpatel017
approved these changes
Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the first of several PRs to implement the Outbox Pattern in order to improve message publishing resilience.
First, we introduce the DatabasePublisher that is able to persist outgoing messages in a database. This operation can be performed in the same transaction as other database operations. It will prevent situations when the database changes succeed, but the message fails to be published.
In a subsequent PR, we'll provide a DatabaseDispatcher implementation that will pull pending messages from the database and publish them on the message queue.