Skip to main content

Book Exercise Lanes

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface​

  • Open learner-facing unit
  • Curriculum path: content/curriculum/architecture/semester-07-architecture-ddd/module-03-domain-driven-design-bounded-contexts/exercises.md
  • App: architecture
  • Semester: semester-07-architecture-ddd
  • Module: module-03-domain-driven-design-bounded-contexts
  • Unit kind: exercise
  • Curation level: module_curated

Learning objectives​

  • Explain Book Exercise Lanes in terms of language, model boundaries, and coordination cost instead of purely diagrammatic DDD vocabulary.
  • Use Book Exercise Lanes to decide where a model should split, who owns it, and how teams should collaborate across boundaries.
  • Use learning-domain-driven-design to connect the learner explanation to bounded contexts, context maps, and strategic design tradeoffs.

Prerequisites​

  • Comfort with modular decomposition, boundaries, and why architecture must align with real problem domains.

Source books​

  • learning-domain-driven-design

Source routes​

Learning Domain Driven Design​

  • /books/learning-domain-driven-design via Khononov: Advantages to exercises, Khononov: Analytical vs transactional data model, Khononov: Anticorruption layer to exercises, Khononov: Appendix A -- Applying DDD case study, Khononov: Appendix A — Applying DDD case study, Khononov: Bounded contexts versus subdomains to science, Khononov: Building blocks part 2, Khononov: Building blocks part 3, Khononov: Building blocks part 4 to exercises, Khononov: BusVNext to exercises, Khononov: Business logic vs architectural patterns, Khononov: Business problems to scenarios, Khononov: Buying a refrigerator to exercises, Khononov: Challenges to exercises, Khononov: Changes in domains to tactical design concerns, Khononov: Comparing subdomains, Khononov: Consistency to tools, Khononov: Cooperation to conformist, Khononov: Customer-supplier to separate, Khononov: Domain knowledge to exercises, Khononov: Event sourcing, Khononov: Event-driven architecture to structure, Khononov: History to building blocks part 1, Khononov: Identifying subdomain boundaries to Gigmaster, Khononov: Inconsistent models to scope of a bounded context, Khononov: Integrating aggregates and outbox, Khononov: Microservices as deep services to aggregates, Khononov: Model translation to stateful model translation, Khononov: Projecting read models to exercises, Khononov: Saga to exercises, Khononov: Search to event-sourced domain model, Khononov: Step 7 read models to exercises, Khononov: Strategic analysis to modernization strategy, Khononov: Strategic modernization to pragmatic DDD, Khononov: Subdomains to exercises (reclassification over time), Khononov: Temporal coupling to exercises, Khononov: Types of events to distributed big ball of mud, Khononov: What is EventStorming to step 6 policies, Khononov: What is a business domain to types of subdomains, Khononov: What is a service to system complexity, Khononov: When to use layered architecture to implementation

Supporting curriculum routes​

No supporting curriculum routes linked yet.

External enrichment​

AI companion modes​

  • Explain simply
  • Socratic tutor
  • Challenge my understanding
  • Diagnose my confusion
  • Connect forward / backward

Source-of-truth note​

This teaching unit is learner-facing guidance. Its canonical source backbone is the referenced book learning-domain-driven-design, and outside material should only clarify or strengthen that backbone.