In software, we are often passing messages around between components, services and even systems. We do so in synchronous and asynchronous ways. But have you stopped to think that our data storage also acts as message passing? Everything we write to storage is, in essence, a message for our future system.

If we use Event Sourcing as our persistence pattern, we are making this message passing in time much more explicit in our software's design. We also align it a lot closer to how we model our business processes to begin with.

This brings with it a lot of benefits. For instance, we are sacrificing a lot less information compared to normalized relational databases. We also enable point-in-time capabilities for our entities. And from a business point-of-view, we are much more likely to be able to fulfill future feature requests based on old data.

This doesn't have to be complex. In this talk, Hannes will give an introduction to what Event Sourcing is, how to fit it into a CQRS architecture, and what design patterns you can use to unlock its full potential.