At Least Once Delivery: Outbox and About 14 Other Patterns
summary
Covers patterns for achieving at-least-once message delivery, focused on the Outbox pattern and about 14 alternative patterns and variants. Compares simplified and complex implementations, showing how each trades off reliability, idempotency, performance and operational cost, and gives criteria to evaluate, choose and defend the right delivery pattern for a given system.
AI-written summary · about
chapters (20)
- 0:0014 patterns for one problem
- 3:18Distributed system problems
- 6:31Transactional consistency
- 10:21Synchronous notifier
- 15:21Naive async notifier
- 18:34Outbox pattern
- 22:53Multi-Outbox pattern
- 24:39Shared Kernel pattern
- 27:48Shared Kernel risks
- 30:21External Coupling pattern
- 32:31Change Data Capture
- 34:00Database replication
- 35:24Snapshot Notifier
- 37:07Real-time Outbox
- 39:19Optimistic notifier
- 41:02Redelivery pattern
- 43:53Inbox pattern
- 47:04Listen to Yourself
- 50:39Edge cases and impact
- 52:03Q&A
related talks
01h 02mMessaging Patterns for Modern Software Solutions
48mOutbox Pattern: When That Shot at the API Isn’t Enough
18mGuaranteed messages delivery:Challenges of transactional Outbox & Inbox patterns
39mDistributed System Messaging: Excuse Me, My Bill Does Not Match My Order
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
50mAt Least Once
01h 02mAt Least Once
01h 03mBeyond Pub/Sub - Advanced Messaging Patterns