Skip to main content

Key Concepts of Domain-Driven Design

Key Concepts of Domain-Driven Design

1. Domain​

The domain is the specific area of knowledge or activity that the software is intended to address.
Understanding the domain is crucial for creating a model that accurately reflects the business requirements.

2. Ubiquitous Language​

A common language shared by both developers and domain experts is essential.
This "ubiquitous language" helps ensure that all stakeholders have a clear understanding of the domain and reduces miscommunication.

3. Bounded Context​

A bounded context defines the boundaries within which a particular model is defined and applicable.
It helps manage complexity by separating different models that may have overlapping terms but different meanings.

4. Entities and Value Objects​

Entities​

  • Objects that have a distinct identity that runs through time and different states.

Value Objects​

  • Objects that describe certain aspects of the domain but do not have a unique identity.

5. Aggregates​

An aggregate is a cluster of domain objects that can be treated as a single unit.
It ensures consistency and encapsulates the rules for modifying its state.

6. Repositories​

Repositories are responsible for retrieving and storing aggregates.
They provide a collection-like interface to access domain objects while abstracting the underlying data storage.

7. Domain Events​

Domain events are significant occurrences within the domain that trigger changes or actions.
They help in capturing state changes and can be used for event-driven architectures.