Outbox Pattern: When That Shot at the API Isn’t Enough
summary
Describes using the Outbox integration pattern to achieve asynchronous communication with eventual consistency when an operation must commit across multiple systems that are not part of a single distributed transaction. Covers the problem of synchronous API calls (failed requests, slow external systems, blocking UI) and presents Outbox as the approach to reliably record changes locally and reliably publish them to external systems without two-phase commit.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:13System communication problem
- 4:03Distributed systems challenges
- 5:50Sync vs async
- 8:01Communication styles
- 12:42Outbox pattern solution
- 16:40Outbox pros and cons
- 20:12Outbox in databases
- 24:25Inbox pattern
- 25:51Outbox storage and processing
- 28:49Reading Outbox messages
- 31:34Message order and duplication
- 35:48Global vs local order
- 36:53Optimizing Outbox structure
- 38:41Outbox vs direct queue
- 40:27Testing Outbox integration
- 42:12Outbox versioning
- 44:43Monitoring and tracing
- 45:45Delivery guarantees
- 47:08Summary and Q&A
related talks
18mGuaranteed messages delivery:Challenges of transactional Outbox & Inbox patterns
58mAt Least Once Delivery: Outbox and About 14 Other Patterns
01h 02mMessaging Patterns for Modern Software Solutions
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
01h 02mAt Least Once
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs
01h 02mAdvanced API and Integration Problems & Patterns
01h 03mBeyond Pub/Sub - Advanced Messaging Patterns