Application Architecture
Module 7
Domain-Driven Design
The strategic half first — bounded contexts, ubiquitous language and context mapping — then the tactical patterns that only pay off once the boundaries are right.
34 min2 lessons
Start moduleWhat you will be able to do
- Identify bounded contexts from language differences rather than from data entities.
- Explain why one shared "Customer" model across a business is a design failure.
- Choose a context-mapping relationship and know what each one commits you to.
- Apply aggregates as consistency boundaries rather than as object graphs.
- Connect bounded contexts to module and service boundaries.
- 11 min
01Bounded Contexts and the Language That Reveals Them
The same word means different things to different parts of a business. Those differences are not sloppiness to be tidied away — they are where the boundaries are.
- 12 min
02Aggregates as Consistency Boundaries
The tactical patterns only pay off inside a correct context. The most misused of them is the aggregate, which is a transaction boundary rather than an object graph.
Domain-Driven Design
6 questions · pass at 75%