Domain-Driven Transformation

on YouTube ↗50m

" summary

Claims that legacy monoliths can be incrementally re‑architected into vertical bounded contexts using a concrete four‑step recipe: re‑discover the domain, model the target architecture, align current code with tools (static analysis, EventStorming and domain storytelling), then do the move by creating empty modules, copying logic, forwarding calls and strangling the monolith. A catalog of refactorings and sprint‑sized tactical steps supports the work; transformation is possible, measurable, and slow but practical.

AI-written summary · about

" chapters (14)

1. 0:00Introduction
2. 2:32Legacy warehouse metaphor
3. 9:30Legacy systems and value
4. 13:26Refactorings for legacy systems
5. 15:00Transforming a monolith
6. 17:53Discovering domain knowledge
7. 21:27Target architecture
8. 24:19Current architecture analysis
9. 27:33Big Ball of Mud problem
10. 34:05Target architecture with bounded contexts
11. 35:51Transformation planning
12. 38:03Extracting bounded context
13. 43:04Conclusion
14. 45:35Q&A

" related talks

• 40mArchitecture Modernization with DDDNick Tune · Øredev 2022
• 37mBuilt to last: A domain-driven approach to beautiful systemsAndrew Hao · RailsConf 2017
• 40mFrom Domain Boundaries to Software ArchitectureNick Tune, Maxime Sanglan-Charlier · Copenhagen Developers Festival 2023
• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 54mDomain-Driven Design and Team Topologies for Product-led OrganizationsNick Tune · NDC Porto 2022
• 01h 05mGetting to DDD: Pragmatic or Principled?Julie Lerman · NDC Oslo 2019
• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 56mAligning Bounded Contexts with Subdomains in Legacy CodeMufrid Krilic · NDC Oslo 2021