Messages, Events, Hubs, and Busses? Oh My
summary
Explains precise selection rules: use Event Grid for discrete, at-least-once pub/sub notifications (file-added pattern, dead‑lettering for failed deliveries), use Event Hub for high-throughput time-ordered streams with capture, retention and replay (millions of events per second, low latency) and use Service Bus for transactional, ordered messages with duplication detection and on‑prem integration; wires these to Azure Functions and durable functions so small handlers scale independently, shown working for IoT telemetry and blob backup flows.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 5:24Application
- 10:26Event Management
- 12:23Event vs Message
- 17:44Message vs Event
- 20:08Event Grid
- 26:49Event Hub
- 29:24Service Bus
- 36:57Questions
related talks
53mAzure Messaging, Queueing, and Events - Which service is right for your solution?
43mAzure Messaging – Streams, Queues, and Pub Sub
35mBuilding Event Driven Integration Architectures
47mA Guide Through The Azure Messaging Services
30mWhat’s new with Azure Messaging
51mImplementing an Event Sourcing strategy on Azure
30mApplication integration patterns for microservices
48mStreaming Azure Services