John Phamvan at DDD Europe 2025
summary
Domain-Driven Design creates a shared understanding via ubiquitous language and drives decomposition of a government agency monolith into bounded-context-aligned components, reducing coupling to legacy systems. Engineers keep ownership of small features without mastering decades-old code, cutting the opportunity cost of maintaining legacy platforms and enabling teams to ship targeted services rather than rewrite everything — effectively removing the requirement to learn COBOL to make minor changes.
AI-written summary · about
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
44mDomain Driven Rearchitecting with the "Domain-from-Legacy" Canvas
37mStart with DDD when you have a monolith
53mDeconstructing the monolith
48mAligning Bounded Contexts with Subdomains in Legacy Code
50mAligning Bounded Contexts with Subdomains in Legacy Code