What Is Domain-Driven Design?

Part II. Tactical Design

In the previous chapters, you learned about tools for sharing knowledge and making strategic decisions—namely, principles for dividing business domains into components and modeling the interactions between them. In this part of the report, you will read about patterns and techniques for implementing those components:

• Chapter 5 describes four different ways of implementing business logic: the transaction script, active record, domain model, and event-sourced domain model patterns.

• In Chapter 6, we will explore different architectural patterns that support the chosen way of modeling the business logic: specifically, the layered architecture, ports & adapters, and CQRS patterns.

• Chapter 7 will discuss technical concerns in implementing interactions between bounded contexts.

Disclaimer

Some of the patterns discussed here deserve a whole book dedicated solely to them. Therefore, the material in this part is presented at a highly introductory level. The goal of these chapters is simply to introduce the patterns and highlight the differences between them.