Implementing Domain-Driven Design
From the domain model to working code
Vernon's practical bridge from Evans' strategic design to tactical implementation: aggregates, domain events, repositories, and the architectures that carry a model into production.
Why CCF Recommends It
Pro begins where Student ended: the model must become code. IDDD shows how a domain model is realized in working systems, giving CCF the implementation layer to reason about.
You Should Understand
- Strategic to tactical DDD
- Aggregates and transactional boundaries
- Domain events and repositories
- Architectures that carry the model
CCF Connection
CCF traces the Concept → Model → Implementation chain: each step must preserve the domain's invariants, and the framework checks whether the implementation honors the model it claims to realize.
CCF Companion
CCF Companion: From Domain Model to Code
How does a concept survive the trip from model to implementation?
Follows the Concept → Model → Implementation chain and shows where reasoning can leak between layers — and how to verify the implementation preserves the model's guarantees.
Where would you like to order?
Prices and availability may change. See the retailer for the current price. Prices last checked 2026-08-08.