Implementing an Event Sourcing strategy on Azure
summary
Shows how to ingest and process high‑throughput events using Azure Event Hubs and persist them into an event store built on Cosmos DB, with working demos of writing, reading and forward and backward playback of streams. Explains options to connect to other Azure services and Kafka‑compatible clients, demonstrates a proven pipeline that scales for millions of events per day, and surfaces tradeoffs (indexing, latency, global distribution) and when to prefer Event Hubs vs Kafka.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:37What is event sourcing
- 4:05Why use event sourcing
- 5:54Event store basics
- 8:01Event playback and state
- 10:03Azure Event Hubs demo
- 12:45Kafka and Azure integration
- 13:48Demo: Event processing
- 16:23Event sourcing in databases
- 17:26Containerized event storage
- 18:30Scalability with Azure
- 20:18Real-time event tracking
- 21:50Azure Functions for events
- 23:18Handling data changes
- 24:26Connecting event systems
- 25:51Client integration needs
- 27:04Summary and takeaways
- 28:18Q&A session
related talks
46mPractical CQRS and Event Sourcing on Azure
35mArchitectures and Trends for Event Stream Processing on Azure with Open Source Software
31mEvent-Driven Architecture - A successful strategy for a journey to the cloud
48mStreaming Azure Services
52mEvent journal in Azure (no Cosmos inside)
52mEvent journal in Azure (no Cosmos inside)
42mBuild a Real-Time Event-Driven Java Solution in Azure
51mThis just happened! Using events in your apps