Almost every application has to deal with state. No matter if you like relational databases or prefer to go NoSQL the result is the same: your application only has one state.
Unfortunately, business requirements are not that static. They change constantly and so do the underlying processes. So how can you prepare your application to quickly adapt to changing processes without constantly migrating your database?
The key to event sourcing is recording what happened and build relevant data models of these events.
In this session, I will guide you through an example project that has been designed with event sourcing and how it compares to a classical CRUD application.