Aligning Bounded Contexts with Subdomains in Legacy Code
summary
A legacy healthcare prescribing system reveals a new subdomain for handling non‑approved medication approvals using Domain Storytelling and the 4+1 Architectural View Models. The team runs a one-week spike in a .NET Visual Studio solution, moves code to create a bounded context, analyzes references and using statements, and introduces a shared kernel to break circular references. End‑to‑end tests expose a runtime coupling that leads to view model composition on the frontend. Lessons: prefer logical separation first, watch introduced dependencies in code reviews, and keep collaborative boundary discovery ongoing.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 3:58Legacy system challenges
- 7:54Four plus one view model
- 17:47Subdomain analysis process
- 21:44Finding bounded contexts
- 27:51Establishing logical boundaries
- 35:39Circular dependencies and fixes
- 40:38Lessons learned and improvements
- 48:11Encouraging future generations
related talks
48mAligning Bounded Contexts with Subdomains in Legacy Code
47mDomain Driven Transformation—How to Bring Back Sustainable Architecture to
41mDomain Re discovery Patterns for Legacy Code
48mDomain Pattern – How the Domain Influences the Architecture
38mDomain-Driven Transformation - how to improve the structure of legacy systems
02h 29mPractical advice for building glorious monoliths
23mArchitecture Remediation
43mPatterns of Legacy Displacement