Messaging Patterns for Modern Software Solutions
summary
Covers concrete messaging fixes: uses Outbox pattern (Entity Framework table + worker) to avoid ghost messages and zombie records, an Inbox pattern to deduplicate retries, and Saga pattern for async workflows with compensating actions; demo uses MassTransit, RabbitMQ, SQL Server and shows outbox/inbox tables, 202 Accepted responses, and message buffering for burst load (load leveling). Explains delivery semantics (at-least-once/at-most-once), duplicate detection windows, and tradeoffs versus HTTP sync request/response.
AI-written summary · about
chapters (16)
- 0:00Messaging patterns intro
- 1:15Monolith to microservices
- 3:50HTTP API problems
- 9:54HTTP limits
- 12:02HTTP for long ops
- 15:38HTTP sync issues
- 19:15Message brokers intro
- 22:47Messaging history
- 25:15Message types
- 28:26Load leveling queues
- 30:12Outbox pattern
- 34:10Ghost messages & zombies
- 37:03Duplicate messages inbox
- 43:00Outbox & inbox demo
- 54:25Saga pattern
- 1:01:24Conclusion and key takeaways
related talks
38mMessaging Patterns to Transform Your Cloud Architecture
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
01h 03mBeyond Pub/Sub - Advanced Messaging Patterns
56mDistributed Messaging patterns
27mApplication Integration Patterns for Microservices
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
58mAt Least Once Delivery: Outbox and About 14 Other Patterns
53mMessaging: The fine line between awesome and awful
