Implement Microservice pattern: Transactional outbox #3330
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.



What does this PR do?
This pull request implements the Transactional Outbox design pattern. It demonstrates how to ensure reliable, at-least-once message delivery from a service by atomically saving business data and its corresponding event in the same database transaction. This PR includes a fully documented code implementation, comprehensive unit tests covering success and failure scenarios, a detailed README and a PlantUML class diagram.
Key features
Customer: The main business entity model that is being created and persisted.OutboxEvent: The entity representing the message to be sent, which is stored transactionally in the outbox table.CustomerService: The service that handles the core business logic, responsible for creating the Customer and the OutboxEvent in a single, atomic transaction.OutboxRepository: The data access layer for reading from and writing OutboxEvent entities to the database.EventPoller: A background process that periodically scans the outbox table for unprocessed events and publishes them to the message broker.MessageBroker: A mock implementation that simulates sending the event to an external messaging system.This pull request is submitted as part of my participation in
Hacktoberfest 2025Closes #2671