Event driven architectures on Azure
summary
Shows how to build event-driven systems on Azure using concrete patterns: write state plus intent in Cosmos and use the transactional outbox with the change feed and a dispatcher to guarantee at-least-once delivery; prefer Storage Queues for simple buffering and Service Bus for ordered, deduped business messages; implement workflows with a Durable Functions orchestrator, or use choreography or a saga via message headers, and consider MassTransit for higher-level abstractions — demonstrated risks like overloading a legacy service with 10,000 requests.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:23Introduction
- 8:09Azure
- 9:21Competing Consumers
- 11:49Two-Phase Commit Transaction Engines
- 17:14Power Automate
- 17:45Logic Apps
- 18:49Durable Functions
- 20:41Activities
- 23:40How Much Information Should We Put in an Event
- 24:00Event Carriage State Transfer
- 28:29Analytical Data
- 30:01Consumer Group
- 31:30Service Bus Service
- 32:04Deduplication Support
- 34:51Cosmos Change Feeds
- 38:43Process Manager
- 45:51Saga Pattern
- 51:56Event Sourcing
- 53:41Request Response
related talks
01h 01mMessage Brokering and Event Driven Architecture on Azure
51mThis just happened! Using events in your apps
55mImplementing scalable messaging patterns in Azure
45mCommon quandaries implementing your first Event Driven Architecture
01h 09mExploring Flow Architectures
56mImplementing an Event Sourcing strategy on Azure
42mImplementing an Event Sourcing Strategy on Azure
46mPractical CQRS and Event Sourcing on Azure