Domain-Driven Design & Team Topologies Hands-on
summary
Hands-on workshop uses a prepared Miro board and physical post‑its to model an online grocery company called Tomati, running timed exercises (12, 10, 15, 10 minutes) to do a domain quiz, spot pivotal events, and propose subdomains. Participants slice event streams into boundaries, then apply independent service heuristics from Team Topologies (cognitive load, dependencies, impact/value) to validate team scope. Example work shows an “add recipe ingredients” service looks too small unless justified by migration or experiment goals, and the process is positioned as iterative rather than prescriptive.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 5:21Hands-on setup and teams
- 7:09Tomati domain and event storming
- 10:45Domain quiz
- 13:59Pivotal events for boundaries
- 22:18Slicing into subdomains
- 24:28Evaluating boundaries
- 28:20Applying heuristics
- 30:06Q&A
- 33:19Closing insights
related talks
54mDomain-Driven Design and Team Topologies for Product-led Organizations
55mDomain Driven Design in practice - how to draw your domain boundaries IRL
38mDomain-Driven Design: Hidden Lessons from the Big Blue Book
57mDomain-Driven Design in Productland
50mDomain Prototyping or Design Is How It Works
50mIt's All About the Domain, Honey - Domain-Focused Architecture with DDD
01h 11mAn introduction to DDD
39mDomain-Driven Design: Hidden Lessons from the Big Blue Book