Event journal in Azure (no Cosmos inside)
summary
A migration from on‑prem MongoDB to a low‑cost Azure design uses Azure Table+Blob with an Azure Function + queue pipeline and C# helpers, trading CosmosDB features for roughly 10x cost savings. Implementation compresses payloads (97% of events fall under the 64KB field limit), offloads oversized blobs, and uses a partition‑prefix secondary‑index pattern to support cross‑entity queries. The journal supports event sourcing and audit use cases, can replay three days of events after an outage, and has production performance comparable to published 20k/sec examples.
AI-written summary · about
chapters (6)
- 0:00Introduction and overview
- 3:36Why event journals matter
- 11:43Event sourcing and CQRS basics
- 22:31Azure storage options for journals
- 35:17Implementing event journal in Azure
- 42:19Conclusion and Q&A
related talks
39mBuilding Event-Driven Systems at Scale with Cosmos DB
51mImplementing an Event Sourcing strategy on Azure
01h 02mFrom SQL to Azure Cosmos DB
20mHow Azure Cosmos DB enables Event Sourcing architecture
20mHow Azure Cosmos DB enables Event Sourcing architecture and powers e-commerce
31mEvent-Driven Architecture - A successful strategy for a journey to the cloud
03h 30mAmericas Live Stream
03h 12mEMEA Live Stream