The Unsung Hero of Modern Software: Asynchronous Messaging
summary
Argues that HTTP request/response becomes brittle at scale and shows concrete alternatives: demos use MassTransit + RabbitMQ to send commands/events, spin up competing consumers, and implement request/reply over queues; demonstrates runtime behavior (messages sit in a dead-letter queue on failure) and a recoverability UI that edits and retries failed messages. Calls out tradeoffs: higher throughput and temporal decoupling but eventual consistency, need for outbox pattern and sagas, and contrasts exactly-once vs at-least-once guarantees.
AI-written summary · about
chapters (12)
- 0:00Introduction to messaging
- 1:06Monoliths to microservices limits
- 8:49HTTP synchronous issues
- 13:25Overlooked system requirements
- 19:43Messaging for loose coupling
- 27:03AMQP and guarantees
- 33:00Throughput and scalability
- 36:09Messaging patterns
- 38:15Messaging tools
- 44:36HTTP vs messaging demo
- 56:49Recovering failed messages
- 1:00:16Key takeaways and closing remarks
related talks
41mForget about HTTP
44mFrom Synchronous to Asynchronous Distributed Microservices
53mYou Keep Using That Word: Asynchronous And Interprocess Comms
01h 01mMessaging: The fine line between awesome and awful
53mMessaging: The fine line between awesome and awful
01h 02mMessaging Patterns for Modern Software Solutions
59mEffective Microservice Communication and Conversation Patterns
47mEverything Loosely Coupled - Advanced Integration Patterns and Their Trade-Offs