[AB#43277] Implemented the transactional inbox for the Catalog Service #251
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
AxTrusov
reviewed
Mar 4, 2024
services/catalog/service/migrations/committed/000011-transactional-outbox-inbox.sql
Outdated
Show resolved
Hide resolved
AxTrusov
reviewed
Mar 4, 2024
services/catalog/service/src/messaging/models/handler-registrator.ts
Outdated
Show resolved
Hide resolved
AxTrusov
approved these changes
Mar 4, 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.
Pull Request
Prerequisites
devfor features andmasterforreleases)
Description
The Catalog Service is now using transactional inbox message handling for reliable handling of publishing messages from the Media and Channel Service.
Release Notes
The Catalog Service is now using transactional inbox message handling for reliable handling of publishing messages from the Media and Channel Service. 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 publishing and publishing messages still work for all media items (movies, TV shows, collections, ...) and Channels.