Implementing an Event Sourcing Strategy on Azure
summary
Describes an end-to-end event sourcing pipeline on Azure using Azure Event Hubs to ingest Kafka-compatible streams, serverless Azure Functions to apply business logic and write events into a Cosmos DB–based event store. Covers using the Cosmos DB change feed for projections and replay, guidance on partition key selection and global distribution for low-latency reads, and demonstrates connectors, transformation functions, an operational dashboard, and high-throughput handling (millions of events) with a live demo.
AI-written summary · about
chapters (17)
- 0:00Welcome
- 3:11Event sourcing principles
- 6:26High-throughput on Azure
- 9:55Kafka integration demo
- 12:23Azure Functions event-driven
- 15:39Cosmos DB change feed
- 18:46Cosmos DB partitioning
- 21:59State reconstruction
- 25:08Optimizing partition keys
- 28:18Monitoring event systems
- 30:50Azure services for event sourcing
- 32:36Closing remarks
- 33:41Q&A: Storing events
- 35:53Q&A: Order exceptions
- 37:19Q&A: High event volumes
- 38:42Q&A: Consistency
- 40:47Q&A: Social media integration
related talks
56mImplementing an Event Sourcing strategy on Azure
52mEvent Sourcing – the what, why & how
46mPractical CQRS and Event Sourcing on Azure
52mEvent Sourcing for the Cloud Developer
57mEvent driven architectures on Azure
45mCommon quandaries implementing your first Event Driven Architecture
01h 01mMessage Brokering and Event Driven Architecture on Azure
57mEventuous Event Sourcing with .NET
