How Azure Cosmos DB enables Event Sourcing architecture
summary
Shows a working e-commerce event sourcing pipeline using Azure Event Hubs, Stream Analytics, Azure Functions and Azure Cosmos DB with the Cosmos DB change feed as CDC; a fake-data generator (Bogus) pumps inventory events and the function materializes a catalog view. Claims reduced API calls from a dozen to two and latency around 150 ms, targets three nines availability by trading synchronous checks for async logs. Demo writes events once, rebuilds state from the ordered event log and updates a serving cache.
AI-written summary · about
chapters (4)
related talks
52mEvent Sourcing – the what, why & how
21mBuild Scalable Inventory System with Azure Cosmos DB
39mBuilding Event-Driven Systems at Scale with Cosmos DB
01h 02mFrom SQL to Azure Cosmos DB
47mWorking with data using Azure Functions
01h 01mServerless & Schemaless with Azure Functions and CosmosDB
27mIntegrating Azure Cosmos DB with the Azure Ecosystem
30mDemystifying Event Sourcing: A Practical Approach to Modern Software Architecture