Aligning Bounded Contexts with Subdomains in Legacy Code
summary
A .NET legacy healthcare prescribing system undergoes strategic DDD using Domain Storytelling and the 4+1 view model to carve a new bounded context for non‑approved medication applications. The team creates a new Visual Studio module, moves code with git, and introduces a shared kernel, but end‑to‑end integration tests fail within a one‑week timebox due to a runtime circular dependency: prescription logic needs past applications. The experiment compiles but doesn’t fully decouple; the pragmatic fix is view‑model composition on the frontend and weekly architectural reviews to continue.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:08Legacy system challenges and team setup
- 7:49Understanding the domain with Domain Storytelling
- 10:58Four plus one view model of software architecture
- 17:07Dependencies and coupling in distributed systems
- 20:35Discovering subdomains in the prescription process
- 23:51From subdomains to bounded contexts
- 27:45Implementing bounded contexts in Legacy code
- 30:36Handling integration tests and dependencies
- 38:09Resolving circular dependencies with view model composition
- 42:07Architectural reviews and lessons learned
- 44:56Q&A and closing remarks
related talks
50mAligning Bounded Contexts with Subdomains in Legacy Code
47mBounded Contexts: Team Topologies and Architecture boundaries aligned
01h 00mFrom Domain Driven Design DDD to Delivery
01h 01mThe DDD Do-Over: Domain-Driven Design Lessons Learned
44mDependencies; Devil or Darling?
51mDomain - Driven Transformation
37mStart with DDD when you have a monolith
48mExperiences scaling a modular monolith to microservices using the 4+1 views