Skip to content

II Tactical Design

Part I decided what to build and where the boundaries go. Part II is about how to build what’s inside those boundaries: how to code the business logic, how to arrange a component’s internals, and how components talk to each other reliably.

  1. Chapter 5 covers two lightweight ways to code simple logic: transaction script and active record.
  2. Chapter 6 brings in the domain model and its building blocks (value objects, aggregates, domain events and domain services) for complex logic.
  3. Chapter 7 adds time to the model: store every change as an event and derive state from the history.
  4. Chapter 8 zooms out to how a component is organized: layers, ports & adapters, and CQRS.
  5. Chapter 9 covers communication between components: translating models, publishing events reliably, and running processes that span several transactions.

Later, Part III puts the tools to work: design heuristics, evolving decisions and EventStorming.

Thread running through Part II: match the tool to the complexity. Simple subdomains get simple patterns, and only the complex core gets the heavier machinery.

5. Implementing Simple Business Logic

6. Tackling Complex Business Logic

7. Modeling the Dimension of Time

8. Architectural Patterns

9. Communication Patterns