Domain Driven Design in practice - how to draw your domain boundaries IRL

on YouTube ↗55m

" summary

After merging four Nordic marketplaces into one company, the team uses domain driven design to redraw boundaries, iterating in Miro/mirror and on the whiteboard, interviewing stakeholders one‑on‑one and running “info time” sessions per team (5–12 people). The concrete outputs are a published domain map, a staffing plan that creates 1 new team (started), splits an overloaded team, and defers one domain; decisions target a 1–2 year rollout and aim to keep one team per domain while tracking evolving ownership.

AI-written summary · about

" chapters (18)

1. 0:00Domain Driven Design intro
2. 5:05What DDD is and why it matters
3. 9:21New real estate vertical
4. 11:30DDD as art not science
5. 18:59First mental model
6. 21:47Forcing stakeholder engagement
7. 26:13Final domain map
8. 29:10Season one recap
9. 31:45Explaining to big boss
10. 35:14Tailoring for tech leads
11. 37:43Presenting to business
12. 41:15Highlighting organizational implications of the map
13. 44:25Info time with tech
14. 46:39Surprise character
15. 49:06Season two recap
16. 50:13Epilogue
17. 51:37Director's cut
18. 54:06Main takeaways

" related talks

• 54mDomain-Driven Design and Team Topologies for Product-led OrganizationsNick Tune · NDC Porto 2022
• 38mDomain-Driven Design & Team Topologies Hands-onNick Tune, Zsófia Herendi · Craft Conference 2022
• 56mMicroservices and Domain-Driven Design — The Strategic PartsRaju Gandhi · Developer Summit 2020
• 01h 04mDomain Driven Design: The Good PartsJimmy Bogard · CodeMash 2018
• 38mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC London 2019
• 47mGetting modules right with Domain-driven DesignMichael Plöd · Spring I/O 2022
• 57mDomain-Driven Design in ProductlandAlberto Brandolini · FlowCon France 2024
• 59mDomain Driven Design: The Good PartsJimmy Bogard · NDC Sydney 2016