Implementing scalable messaging patterns in Azure
summary
Compares Azure Event Grid, Event Hubs, Service Bus and Storage Queues with concrete limits and guarantees: Event Hubs ingests millions of events per second with at least once semantics, Service Bus offers FIFO, duplicate detection, transactions, sessions and dead‑lettering, and Storage Queues can hold roughly 80 GB per queue. Shows practical implementations: claim check for large payloads, competing consumers with Azure Functions scaling on queue depth, session IDs for ordered processing, and Saga orchestration versus choreography trade‑offs.
AI-written summary · about
chapters (11)
- 0:00Scalable messaging in Azure
- 2:11Events vs messages
- 4:19Azure messaging services
- 10:20Publish-subscribe pattern
- 15:19Request-reply pattern
- 19:12Claim check pattern
- 22:23Priority queues
- 29:10Competing consumers pattern
- 38:21Sequential convoy
- 43:15Sagas
- 52:00Key takeaways
related talks
01h 01mMessage Brokering and Event Driven Architecture on Azure
57mEvent driven architectures on Azure
01h 09mExploring Flow Architectures
01h 03mChoosing the Right Messaging Solution for Your Architecture
51mThis just happened! Using events in your apps
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
42mIt's like 10,000 streams when what you need is a queue
38mMessaging Patterns to Transform Your Cloud Architecture