Building Event Driven Integration Architectures
summary
Defines discrete vs series events and maps Azure services: Service Bus for transactional messaging, Event Hubs for replayable, partitioned event streams, and Event Grid for push notifications with CloudEvents support. Claims Event Grid pushes (designed for ~10M events/sec per region, cited 2.2 trillion/day) with 24‑hour retry and ~64KB payload limits. Shows a working demo: blob-created → Event Grid → webhook (filtered for JPEG) and a VM-resize → Event Grid → Logic App → Azure Function → table lookup that sends a high‑priority alert email when size violates policy.
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:50Messaging vs Eventing
- 4:05EventDriven vs Event Sourcing
- 4:58Why EventDriven Integration
- 7:53Messaging vs EventDriven
- 12:03Messaging vs Appending
- 13:37Communication Patterns
- 13:58CloudNative Schema
- 15:25Event Grid
- 17:15Event Handler
- 19:16Limitations
- 20:13Publishing
- 21:41Service Bus
- 22:45Demo
related talks
43mMessages, Events, Hubs, and Busses? Oh My
31mEvent-Driven Architecture - A successful strategy for a journey to the cloud
53mAzure Messaging, Queueing, and Events - Which service is right for your solution?
47mA Guide Through The Azure Messaging Services
43mAzure Messaging – Streams, Queues, and Pub Sub
51mImplementing an Event Sourcing strategy on Azure
52mEvent journal in Azure (no Cosmos inside)
43mDesigning software in the cloud