-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Foundation utilities to support the CDC outbox-pattern #8698
Comments
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
Pushed to the next |
- Provide repostiroy that represents the database that stores the business entities and message outbox. - Provide event abstraction and event sender service. - Default implementation for the event sender service that converts the events into entities and persist them into the outbox db. Related to spring-projects#8698
Can you illuminate me on why this can't be achieved with a JdbcChannelMessageStore-backed QueueChannel? |
See the pattern page: https://microservices.io/patterns/data/transactional-outbox.html. In the end there are a couple links like this:
So, the |
As part of your business logic, you often need to create/update/delete your local data store and simultaneously send messages/events to a message broker. Furthermore you need to guarantee the atomicity of both operations (e.g. the message can be sent only if the database transaction is successful). The (2PC) is not a scalable and often not supported option for most distributed systems.
The outbox pattern provides an approach for letting services execute these two operations in a safe and consistent manner.
Spring Integration can provide common utilities to facilitate the creation and management of Outbox table and entities as well as common outbox messaging abstraction.
References:
The text was updated successfully, but these errors were encountered: