Domain-Driven Design & Team Topologies For Product-led Organizations

on YouTube ↗49m

" summary

Runs practical examples: uses Event Storming workshops to map value streams and finds a messy data‑cleaning bug that propagates across teams, two teams discover an existing API and ship a fix the same day. Applies Team Topologies heuristics (small 5–9 stream-aligned team sizes, interaction modes) to reveal an overloaded integration platform with too many collaborations and no budget. Uses DDD’s core supporting generic subdomains and charts to prioritize a supporting area that involves 30 people, warns large legacy monoliths (50k rules C++) take years.

AI-written summary · about

" chapters (5)

1. 0:00Start
2. 26:02Team Topologies: What is a team, what is the cognitive limit?
3. 28:19Team Topologies Interaction Modes
4. 35:59Core, Supporting, and Generic Domains
5. 44:39Modernization Core Domain Charts

" related talks

• 54mDomain-Driven Design and Team Topologies for Product-led OrganizationsNick Tune · NDC Porto 2022
• 39mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · NDC Oslo 2018
• 41mDomain-Driven Design: Hidden Lessons from the Big Blue BookNick Tune · Craft Conference 2019
• 29m20 Years of Domain-Driven Design: What I’ve Learned About DDDEberhard Wolff · WeAreDevelopers World Congress 2025
• 41mEfficient Domain-Driven Design: An Introduction to Event StormingArne Blankerts · phpDay 2019
• 41mArchitecture for Flow with Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · Øredev 2022
• 44mArchitecture for Flow - Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · DDD Europe 2022
• 45mArchitecture for Flow with Wardley Mapping, DDD, and Team TopologiesSusanne Kaiser · Craft Conference 2022