[AB#43277]Transactional inbox outbox messaging for the Entitlement Service #252
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.
Pull Request
Prerequisites
dev
for features andmaster
for releases)Description
The Entitlement Service is now using transactional inbox message handling for reliable sending and processing of messages.
Release Notes
The Entitlement Service is now using transactional inbox message handling for reliable sending and processing of messages. Outgoing messages are stored as part of the business transaction in the outbox database table. From there they are sent via RabbitMQ. Incoming messages are received from RabbitMQ and stored in the "inbox" database table. The transactional message handlers ensure then an exactly-once message processing.
Testing Notes
Messaging should work just like before - but survive server crashes and DB outages. Please test that all the sent (synchronize claim definitions) and received messages (synchronize claim definitions finished/failed, claim set published, and subscription plan published) still work.