Strategic Domain-Driven Design is about communication and collaboration. But once you have strategized, communicated, and collaborated, where do you put the code you write? That’s where this book fits.

I’m taking a “code first” approach and here’s why. There’s been a strong tendency for developers to jump straight to the “tactical” patterns of Domain-Driven Design because they’re concrete and relatively straightforward to implement. The abstract concepts such as “Bounded Context” are much less obvious.

Strategic Domain-Driven Design tells us that our code should fit inside one or more Bounded Contexts. But what is a Bounded Context, and where should we draw the boundary?

The answer is, “it depends on the situation”, which is not terribly helpful when we need to actually start implementing a feature. The problem, literally, is in figuring out where to start.

Here is where to start.