Event Sourcing: When It's Right, When It's Overkill
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/concepts/cluster-05-ddd-in-practice/14-event-sourcing-when-right-when-overkill-primary.md - App:
architecture - Semester:
semester-07-architecture-ddd - Module:
module-03-domain-driven-design-bounded-contexts - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain Event Sourcing: When It's Right, When It's Overkill in terms of language, model boundaries, and coordination cost instead of purely diagrammatic DDD vocabulary.
- Use Event Sourcing: When It's Right, When It's Overkill to decide where a model should split, who owns it, and how teams should collaborate across boundaries.
- Use
learning-domain-driven-designto 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
Learning DDD: Bounded Context 3 -- Event Crunchers,Learning DDD: Bounded Context 3 — Event Crunchers,Learning DDD: Event Sourcing,Learning DDD: Search to Event-Sourced Domain Model
Supporting curriculum routes
No supporting curriculum routes linked yet.
External enrichment
- Context Mapper Documentation (
official_docs_companion) - Connects DDD strategic design concepts to a concrete, inspectable modeling workflow. - DDD Crew Context Mapping Patterns (
read_if_stuck) - Helps learners keep context-map relationship vocabulary practical instead of abstract.
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.