Architecture Modernization with DDD

on YouTube ↗40m

" summary

Claims a concrete modernization path: use Event Storming and Domain Message Flow Modelling to map domains, then validate boundaries with process modeling and a bounded context canvas. Gives numbers: a startup builds an online car dealership in 90 days while a legacy company spends a year without pushing one line to the cloud. Describes a five‑team workshop where a 90% data‑clean issue is exposed and an API is hooked up that evening. Points to a starter modeling process and GitHub resources.

AI-written summary · about

" chapters (12)

1. 0:00Architecture modernization with DDD
2. 3:14Software delivery slows down
3. 5:02Modernization challenges
4. 7:33DDD for fast team workflows
5. 9:44Architecture and business needs
6. 13:15Event storming for domains
7. 17:25Decomposing domains
8. 22:00Domain boundaries deep dive
9. 28:18End-to-end domain workflows
10. 33:09Design choices for subdomains
11. 37:02Principles of modernization
12. 38:27Start modernization journey

" related talks

• 40mArchitecture Modernization: Aligning Software, Strategy, and StructureNick Tune · Copenhagen Developers Festival 2023
• 01h 12mArchitecture Modernization: Aligning Software, Strategy, and StructureNick Tune · NDC Sydney 2024
• 48mArchitecture Modernization: Aligning Software, Strategy, and StructureNick Tune · NDC London 2024
• 48mArchitecture Modernization: Aligning Software, Strategy, and StructureNick Tune · NDC Porto 2023
• 50mDomain-Driven TransformationHenning Schwentner · DevDays Europe 2024
• 51mUXDD: A New Pragmatic Methodology for Domain Modeling and User Experience.Dino Esposito · .NET Fest 2017
• 47mArchitecture for Flow with Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · KanDDDinsky 2022
• 46mMaster Software Architecture: From Simplicity to ComplexityMaciej «MJ» Jedrzejewski · GOTO Copenhagen 2025