Messaging: The fine line between awesome and awful
summary
A monolith migrates to messaging and performance gets worse: UI shows stale data, duplicates and out‑of‑order handlers create side effects, and tracing becomes a nightmare. The fix is explicit decoupling into subdomains, picking request‑response, publish‑subscribe or one‑way per requirement, and using orchestration or choreography for complex prerequisites. Use future messages (Azure Service Bus, Amazon SQS, RabbitMQ), the outbox pattern, deduplication IDs, sagas for distributed commits, and OpenTelemetry for observability.
AI-written summary · about
chapters (8)
- 0:00Monolith to messaging disaster
- 5:19Who I am and why I’m here
- 12:03Decoupling systems
- 24:26UI consistency in async
- 29:47Out-of-order messages
- 38:14Troubleshooting failures
- 41:43Duplicate messages
- 49:54Summary
related talks
01h 01mMessaging: The fine line between awesome and awful
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
01h 02mMessaging Patterns for Modern Software Solutions
01h 03mBeyond Pub/Sub - Advanced Messaging Patterns
38mMessaging Patterns to Transform Your Cloud Architecture
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us
01h 01mMessage Brokering and Event Driven Architecture on Azure