Azure Messaging, Queueing, and Events - Which service is right for your solution?
summary
Compares Event Hub, IoT Hub, Event Grid, Service Bus (queues/topics) and Storage Queue with concrete tradeoffs, code snippets and demos. Event Hubs target high-throughput streaming, partitions limit to 32 and throughput units map to ~1 MB or 1k events/sec each, captures to blob and uses consumer groups for independent reads. Event Grid handles one‑off Azure events with retries. Service Bus gives ordered queues, at‑most‑once vs at‑least‑once locks and sessions, and topics for filtered pub/sub. Storage Queue is cheaper but has 64 KB message limit and no ordering guarantee.
AI-written summary · about
chapters (7)
- 0:00Welcome
- 3:57Azure Event Hubs for streaming
- 17:34Event Grid for events
- 28:34Service Bus queues
- 35:43Service Bus topics
- 45:02Storage queues
- 52:02Summary
related talks
43mAzure Messaging – Streams, Queues, and Pub Sub
47mA Guide Through The Azure Messaging Services
43mMessages, Events, Hubs, and Busses? Oh My
01h 16mChoosing the Right Messaging Solution for Your Architecture
01h 03mChoosing the Right Messaging Solution for Your Architecture
35mBuilding Event Driven Integration Architectures
30mWhat’s new with Azure Messaging
50mMiddleware Showdown: Exploring Diverse Messaging Solutions