Distributed Messaging patterns
summary
Demos use .NET code to show concrete patterns: an ASP.NET Core API returns HTTP 429 with a Retry-After header and a worker uses Polly retries to back off; a load generator sends hundreds of messages to Azure Service Bus while multiple processors scale out to drain a queue (counts observed in the hundreds); a local RabbitMQ forwards to cloud via a RabbitMQ shovel for store-and-forward resiliency; Docker Compose and Azure alerts automate scaling.
AI-written summary · about
chapters (22)
- 0:00Introduction to messaging patterns
- 1:24Direct messaging approach
- 2:50Brokered messaging approach
- 3:33Broadcast messaging approach
- 5:19Handling messaging challenges
- 6:02Importance of messaging protocols
- 8:08Synchronous vs asynchronous communication
- 9:51Synchronous throttling patterns
- 11:39Reverse proxy for load balancing
- 13:45Client-side retry strategies
- 15:30Demo: Throttling and retries
- 23:36Asynchronous messaging patterns
- 24:18Long-running work with queues
- 25:44Reply queues and dead letter queues
- 27:31Load leveling with queues
- 29:16Scaling consumers dynamically
- 31:02Publish-subscribe patterns
- 32:45Handling sparse connectivity
- 34:35Demo: Queue processing and scaling
- 42:59Demo: Publish-subscribe implementation
- 48:56Demo: Sparse connectivity with RabbitMQ
- 52:46Summary and resources
related talks
38mMessaging Patterns to Transform Your Cloud Architecture
52mDIY Async Message Pump: Lessons from the trenches
01h 02mMessaging Patterns for Modern Software Solutions
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
46mDIY Async Message Pump: Lessons from the trenches
46mDIY Async Message Pump: Lessons from the trenches
55mForget about HTTP
55mImplementing scalable messaging patterns in Azure