Distributed System Messaging: Excuse Me, My Bill Does Not Match My Order
summary
Explains why exactly‑once delivery is impossible in general and focuses on effectively once processing with concrete fixes: duplicate detection via a processed‑messages table, deterministic GUIDs for downstream dedupe, and the outbox pattern that stores outgoing events atomically with business state. Shows a live failure mode called ghost messages and how each fix shifts but does not fully eliminate risk (storage growth, ordering issues). Demos and tradeoffs are explicit.
AI-written summary · about
chapters (8)
- 0:00Start
- 9:57The User Interface
- 12:49Method That Processes the Add Item Message
- 21:13Ghost Message
- 22:40Idempotence
- 30:57Publish the Downstream Messages
- 31:12Deterministic Message Ids
- 35:21The Outlooks Pattern
related talks
01h 01mMessaging: The fine line between awesome and awful
01h 02mConsistency and Agreements in Distributed Systems
58mAt Least Once Delivery: Outbox and About 14 Other Patterns
44mSafe Passage: Messaging in Microservice Environments
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
01h 02mMessaging Patterns for Modern Software Solutions
01h 03mBeyond Pub/Sub - Advanced Messaging Patterns
01h 02mAt Least Once