Thinking events, fast and slow

Are you familiar with the distinction between System 1 and System 2 of your brain? System 1 is fast and based on instinct. System 2 is slower and more logical. Once you become proficient with doing something, System 2 has learned System 1 how to do it based on repetition and practice. It makes up 98% of your thinking capacity.

Right now, your System 1 is trained in relational databases. It 'feels' database table structures and the denormalization required to keep it in order instinctively. It's what it has always known. Thinking in data has become the norm, while life and businesses are based on events.

We realized that using events between microservices is useful. But how do we move from thinking in relational databases to thinking in events? What are the tools that enable you to do so? We'll take a look into Eventstorming, Eventmodelling and Domain Storytelling. We will see how easy it is to create an application based on these techniques and the events they have made us aware of.

Last but not least, you will get some suggestions on how to try this out in your team step by step to achieve the cultural change needed for this transition! You won't regret teaching your team's System 1 this way of thinking, I promise.

Short description

System 1 is fast and based on instinct. System 2 is slower and more logical. Once you become proficient with doing something, System 2 has learned System 1 how to do it based on repetition and practice. It makes up 98% of your thinking capacity.

Right now, your System 1 is trained in relational databases. It 'feels' database table structures and the denormalization required to keep it in order instinctively. It's what it has always known.

We realized that using events between microservices is useful. But how do we move from thinking in relational databases to thinking in events?