#52 FREE Ebook: Understand Your Domain First: An Introduction to Event Storming and Domain-Driven Design

Four months of silence later, I have transformed my "good enough" Domain-Driven Design book into something that actually teaches you how to think about business domains.

Radio silence since March, right? I know, I know – where the hell have I been?

I have been completely obsessed with something that's been eating at me since I published "Master Software Architecture: A Pragmatic Guide."

Don't get me wrong, that book helped thousands of architects. But when I looked back at my first attempt at strategic Domain-Driven Design – "Mastering Strategic Domain-Driven Design" from late 2023 – I realized I could have done much better.

Sure, it hit 1,000 downloads in 24 hours and people loved that it was totally free. But I kept thinking that this is not good enough. You deserve better.

So I made a decision that probably sounds crazy to most creators. I completely stopped writing my newsletter and poured every ounce of my writing energy into rewriting that book from scratch.

Starting in March, I began what turned into a complete reconstruction—not a revision, not an update, but a total rebuild from the foundation up.

The original was good. This new version? It is the book I wish I had when I was struggling to understand why my software projects kept missing the mark despite perfect technical execution.

I am happy to share with you "Understand Your Domain First: An Introduction to Event Storming and Domain-Driven Design." I used some parts of the "Master Software Architecture” book in it (just that you know).

Most technical books teach you patterns and frameworks. This book teaches you how to think. It shows you how to look at a business domain and see the natural seams where your software should split, the workflows that drive real value, and the integration challenges that will emerge before they become expensive problems.

When you finish this book, you will know how to use Event Storming and transform the results of it into subdomains, bounded contexts and how to define a context map. Thanks to it, you will be able to understand any business domain deeply enough to build software that serves the business instead of fighting against it.

Download it, share it, use it to transform how you and your team think about software architecture.

And of course, let me know what you think :)