Domain - Driven Transformation
Talkat JCON Europe 2023 · on Wednesday, 2023-06-21· at 12:00· Cinema Blackbox, Im Mediapark 1, 50670 Köln, Germany·
summary
Claims a reproducible four‑step path: domain rediscovery, design the ideal bounded‑context architecture, map that onto the monolith, and migrate via many small refactorings. Uses collaborative modeling (domain storytelling / event storming), a public catalog of domain‑driven refactorings, and a concrete example: carve Sales and Risk Assessment from a leasing monolith by duplicating and then pruning a Contract model, extracting voteContract into a new Risk service, and deploying each compiling step. Advocates the strangler fig application over big‑bang rewrite and running a transformation backlog alongside product work.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:30About me
- 3:35Storytelling
- 5:53Monolith
- 9:15Typical diseases
- 10:59Refactories
- 13:58Control Complexity
- 15:34Domain Driven Transformation
- 17:21Problem with Complexity
- 18:01Problem with Big Systems
- 22:00Modernization Options
- 25:18Strangler Fig
- 28:26Domain Rediscovery
- 30:11Collaborative Modeling
- 36:20Context Map
- 42:54Transformation Backlog
- 45:04Step 4 Do the Move
related talks
47mDomain Driven Transformation—How to Bring Back Sustainable Architecture to
38mDomain-Driven Transformation - how to improve the structure of legacy systems
48mDomain Pattern – How the Domain Influences the Architecture
01h 00mFrom Domain Driven Design DDD to Delivery
44mDomain Driven Rearchitecting with the "Domain-from-Legacy" Canvas
37mStart with DDD when you have a monolith
48mDomain Driven Design: The Good Parts
38mWhat I talk about when I talk about Domain Driven design