Aligning Bounded Contexts with Subdomains in Legacy Code
summary
Attempt to carve a bounded context out of a legacy .NET prescription system aims to align subdomains with code by moving projects into a new Visual Studio solution, applying 4+1 architectural view model thinking and strategic DDD context mapping. Team extracts common types into a shared kernel using the stable abstraction principle, runs only unit tests to keep feedback fast, then discovers a circular logical dependency (physicians need prior-application data) and solves it with view-model composition and weekly architectural reviews.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:35Training and Coaching
- 4:14Core Domain
- 6:50Problem Space and Solution Space
- 9:27The Two Pillars of DDD
- 10:36Making Sense of the Problem Space
- 11:27Reducing the Cognitive Load
- 13:07Observable boundaries
- 18:19Logical View Dependencies
- 19:52Cost of Dependencies in a Distributed System
- 37:48Integration tests?
- 40:25Stable Abstraction Principle
- 46:44View Model Composition
related talks
01h 01mBounded Contexts: Manage the Understandability of Your Systems
50mDomain-Driven Transformation
55mCharting the uncharted: Discovering and evolving bounded contexts
40mFrom Domain Boundaries to Software Architecture
44mDependencies; Devil or Darling?
47mBlending Product Thinking with Architecture
37mBuilt to last: A domain-driven approach to beautiful systems
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies