Implementing an Event Sourcing strategy on Azure

In recent years the Event Sourcing pattern has become increasingly popular. By storing a history of events it enables us to decouple the storage of data from the implementation of the logic around it. And we can rebuild the state of our data to any point in time, giving us a wide range of opportunities around auditing and compensation.

In this demo-heavy session you will learn how we can use Azure Event Hubs to process and store these events to build our own event store based on Cosmos DB. Moreover, we will also dive into options around connecting to other Azure services and even Kafka applications to easily implement this popular pattern in our own solutions.

#azurecosmosdb #azure #nosql #cloud #cosmosdbconf

[igorgolovko]

Great video with a good explanation of what is event sourcing and how it could be used with Azure Cosmos DB.
Looking forward to seeing further videos from this area.

[edgeofsanitysevensix]

Great video. For materialized views, would RDBMS be ok for this since some of my clients prefer this? We'd just grab the Cosmos event as you demo here but maybe use SQL to store the relational data?

[edwardlandon]

Hi, that was great, thanks. Do you have a link for the source code please?

[ZerX]

Two critiques. 1. Scrolling... Slow down! I was watching this on my tv and rewinding in 10 second units because your flying up and down is painful. 2. Present in Zen Mode in VS Code. With such low resolution it's hard to read combined with point 1. We don't really need to focus on the Treeview or Terminal window.

[AFellowGentleman]

And re-hydrating the aggegates every time and all that other complexity which comes with eventual consitent projections etc costs nothing.