Event sourcing reconstructs an entity's current state by replaying a historical sequence of immutable events rather than storing the final state.
The insert-only nature of event sourcing avoids database locking and scaling issues common in CRUD models while providing a natural audit trail.
An overview of key Azure services for an event-driven system, including Cosmos DB for storage, Event Hubs for ingestion, and Service Bus for commands.
Azure Functions simplify development by using triggers and bindings to connect services like Cosmos DB and Event Hubs without writing boilerplate code.
A detailed walkthrough shows how services connect to ingest order data, store events, and trigger downstream processes like invoicing.
Use the Cosmos DB Change Feed with Azure Functions to create pre-calculated, denormalized data projections that make querying fast and efficient.
The full architecture diagram is revisited to show how materialized views fit in, serving pre-aggregated data to dashboards and client applications.
A summary of best practices highlights using Cosmos DB as an append-only store and leveraging the Azure ecosystem like a box of Lego bricks.
25:41Radu Vunvulea
43:26Markus Möller
47:38Menaka Baskerpillai
40:32Matthias Falkenberg & Timo Knapp
27:33Gerard Klijs
43:27Allard Buijze
24:22Jürgen Pilz
45:48Denis Washington & Olli Salonen
Jobs that call for the skills explored in this talk.
PRODYNA SE
Düsseldorf, Germany
PRODYNA SE
Hamburg, Germany
Agiliz