An introduction to DDD

on YouTube ↗01h 11m

" summary

Domain Driven Design claims that ubiquitous language and small, tactical models beat vague patterns more often than not, so teams run cheap workshops (Post‑its, event storming, photos) to extract terms, build a glossary and a context map, then implement one bounded area at a time. Examples: a Tube‑map style model clarifies scope, a WordPress wiki sustains the glossary, and incremental refactors around bounded contexts prevent the codebase turning into a big ball of mud.

AI-written summary · about

" chapters (13)

1. 0:00Welcome and introduction to Domain Driven Design
2. 3:51Strategic vs tactical design
3. 8:26Domains and domain models
4. 14:33Ubiquitous language
5. 21:30Knowledge crunching
6. 25:07Event storming
7. 28:18User story mapping
8. 30:46Event modeling
9. 34:23Bounded contexts
10. 39:08Tactical design patterns
11. 46:58DDD architectural patterns
12. 53:00Why strategic DDD matters
13. 54:12Q&A

" related talks

• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 58mDDD really matters!Jimmy Nilsson · NDC Sydney 2019
• 01h 05mGetting to DDD: Pragmatic or Principled?Julie Lerman · NDC Oslo 2019
• 38mIntroDDDuctionRobert Basic · Laracon EU 2018
• 50mIt's All About the Domain, Honey - Domain-Focused Architecture with DDDH. Schwentner · code.talks 2017
• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 01h 04mDomain Driven Design: The Good PartsJimmy Bogard · CodeMash 2018
• 59mDomain Driven Design: The Good PartsJimmy Bogard · NDC Sydney 2016