Domain-Driven Design for Software Design and Architectures
Domain-driven design is an approach that organises software around the business domain. Strategic DDD defines bounded contexts, a ubiquitous language and context maps, while tactical DDD models inside a context with entities, value objects, aggregates, domain events and repositories, so code reflects how the business talks.
Stage: Domain and Quality · Part of the Software Design and Architecture roadmap · Last reviewed 19 November 2026
What to learn in Domain-Driven Design
- Run a short event storming session to find domain events
- Split a domain into bounded contexts and name their relationships
- Model a concept as a value object instead of a primitive
- Design an aggregate with one root and enforce its invariants
- Raise domain events when something meaningful happens
- Decide where domain logic lives compared with application services
Domain-Driven Design interview questions
What is the difference between an entity and a value object?
An entity has an identity that persists as its attributes change, such as an order with an id. A value object is defined only by its values, is immutable and interchangeable, such as money or an address.
What is an aggregate in DDD?
An aggregate is a cluster of related objects treated as one unit for consistency, with a root entity that controls access. Invariants are enforced within the boundary, and other aggregates are referenced by id, not held directly.
Where Domain-Driven Design fits in the Software Design and Architecture roadmap
Domain-Driven Design belongs to the Domain and Quality stage (advanced level). Model the business.
Other units in this stage
Back to the full Software Design and Architecture roadmap