Domain Driven Transformation—How to Bring Back Sustainable Architecture to
summary
Shows a concrete four‑step recipe: domain rediscovery, model the greenfield target, align the monolith to that model, and move incrementally. Uses collaborative modeling (domain storytelling, event storming), a catalog of domain‑driven refactorings, and sprint‑sized technical steps. Demonstrates extracting the risk assessment bounded context from a 20–25 year leasing monolith by creating an empty namespace, copying voteContract, switching callers, deploying, then deleting the old code. Emphasizes measurable modularization, stabilized CI/CD first, and evolutionary, deployable changes.
AI-written summary · about
chapters (15)
- 0:00🚀 Introduction: A Story of Transformation in Software and Architecture
- 3:00The Legacy System: Problems with Old Monolithic Software
- 7:00How to Approach Legacy Systems: Modernize, Don’t Replace
- 9:30Understanding Domain Knowledge Hidden in Legacy Software
- 12:00The Need for Modularization in Legacy Systems
- 15:00Identifying and Diagnosing the "Diseases" of Legacy Systems
- 18:00Strategic vs. Tactical Refactoring: A Two-Pronged Approach
- 21:00Domain Rediscovery: Putting the Legacy System Aside to Understand the Problem
- 24:00Modeling the Ideal Architecture and Target State for Modularization
- 26:00Aligning Current Architecture with Target Architecture
- 29:00Breaking Down Monolithic Code: Identifying Boundaries and Subdomains
- 33:00The Role of Domain Storytelling and Collaborative Modeling
- 36:00Moving From Monolith to Modularization: Step-by-Step
- 39:00Technical and Socio-Technical Transformation: How to Organize Teams for Success
- 42:00Conclusion: Embrace Small, Evolutionary Steps in Domain-Driven Transformation
related talks
51mDomain - Driven Transformation
38mDomain-Driven Transformation - how to improve the structure of legacy systems
48mDomain Pattern – How the Domain Influences the Architecture
48mDomain Driven Design: The Good Parts
44mDomain Driven Rearchitecting with the "Domain-from-Legacy" Canvas
38mWhat I talk about when I talk about Domain Driven design
01mJohannes Rost
55mDomain-Driven Design: back to the roots
