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.
In the demo we will show how we can use order events to fill our data store. Below is an example of such an event.
{
"id": "6a0597ae-c137-45a8-932b-45994341dce6",
"eventTime": "2021-03-29T17:07:15.8743603+02:00",
"orderNumber": "1b8211e0-f1b6-4261-8487-58a065ab1613",
"orderStatus": "REQUESTED",
"hubId": 258,
"customer": {
"customerId": 321,
"deliveryAddress": {
"name": "John Smith",
"street": "Pariser Platz 1",
"city": "Berlin",
"zipCode": "10117"
}
},
"delivery": {
"plannedDeliveryTime": "13-04-2021 19:00",
"pickingStartTime": "13-04-2021 17:00",
"pickingEndTime": "13-04-2021 17:05",
},
"articles": [
{
"article": "Coca-Cola Cherry",
"quantity": 5,
"price": 2.95
},
{
"article": "Jim Bean",
"quantity": 1,
"price": 9.95
}
]
}