Azure Messaging – Streams, Queues, and Pub Sub
summary
Overview of Azure messaging tools with concrete tradeoffs and numbers: Service Bus offers JMS2‑style queues, topics, sessions and dead‑lettering for single‑processing and transactional workflows; Event Hubs is a high‑throughput, Kafka‑protocol compatible event stream with 10 ms end-to-end latency and partitioned append‑only logs; Event Grid provides an MQTT 5.0 broker and 24‑hour retry buffering for webhook receivers; Fabric Event Streams and Stream Analytics integrate real‑time pipelines. Azure reports 400 trillion requests per month and supports Kafka protocol compatibility and MQTT 5.0 broker across multi‑zone and geo‑replicated clusters.
AI-written summary · about
chapters (9)
- 0:00Introduction and overview
- 5:28Why multiple messaging services
- 10:50Event Grid explained
- 20:34Service Bus deep dive
- 26:22Event Hubs and streaming
- 30:56Architecture and reliability
- 37:24Geo-replication and disaster recovery
- 40:35Workload isolation and storage
- 42:00Closing remarks
related talks
47mA Guide Through The Azure Messaging Services
53mAzure Messaging, Queueing, and Events - Which service is right for your solution?
30mWhat’s new with Azure Messaging
43mMessages, Events, Hubs, and Busses? Oh My
35mArchitectures and Trends for Event Stream Processing on Azure with Open Source Software
51mThis just happened! Using events in your apps
48mStreaming Azure Services
35mBuilding Event Driven Integration Architectures