Strategic DDD
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
use strategic domain-driven design to decide where models and team boundaries belong.
Planned topics
- A bounded context is a boundary inside which a model and its words mean one thing.
- "Customer" means different things to billing, support, and marketing; separate contexts keep each model clean.
- Ubiquitous language: the team and domain experts use the same words in talk and code.
- Strategic design is about boundaries and relationships between contexts, not class diagrams.
Draft outline details
Demonstration
three boxes for the marketplace (Listings, Orders, Seller Payouts) each defining "seller" differently, with the words each context uses.
Check your understanding
Why keep separate models of "customer" in separate contexts?
Show answer
Each context needs its own meaning; one shared model grows contradictory and couples teams.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.