This might seem a lot for just a single chapter. And yes, to be honest, the topics mentioned are a book per bullet. The idea here is to give a little bit of taste and try to capture its core essence. So, where does it all start then? Well, in this setting, this is really easy. DDD was first coined by Eric Evans in 2003 in his book of the same name. He wrote about how to tackle complexity in software, and from his experience we have found techniques, patterns, and practices that go together and form a mindset that we can use to approach software development with.

In this mindset, it's not only a certain way of working but also a set of core values that are very well-aligned with delivering high quality software that meets the users' requirements. After all, for the most part, we as developers go to work to create something for others to use. It's all about adding business value, and DDD can be the tool to do just that. I would argue that DDD is applicable for most...