From EventStorming to CoDDDing
summary
EventStorming is used to extract precise domain events (example: ticket requested, seats reserved) and turn them into aggregates and tests so code mirrors business language; the team runs big‑picture workshops with sticky notes, moves to TDD unit tests, and implements happy‑path behaviors plus domain exceptions (e.g. no seats available, reservation timeout). Workshops reveal policy gaps (split seating, payment timeouts) that become lightweight features or monitored events, and the resulting code compiles the language into enforceable invariants.
AI-written summary · about
chapters (16)
- 0:00Introduction to talk
- 1:07Waterfall and knowledge loss
- 3:57Anemic domain model problem
- 6:03Illusion of knowledge in coding
- 8:08Open office communication barriers
- 8:50Event storming origins and purpose
- 13:50Event storming workshop demo
- 21:00From event storming to coding
- 23:06DDD value objects and entities
- 28:43Modeling aggregates and invariants
- 31:31TDD with event storming insights
- 37:27Implementing movie screening domain
- 42:05Hexagonal architecture overview
- 44:10Learning and Symmathesy in software
- 45:13Q&A on split seat events
- 47:21Combining BDD with event storming
related talks
01h 02mEvent Storming for domain-driven design
31mHow EventStorming Transformed Our Domain Modeling Process
14mSession 1: Event Storming
47mESSENTIALS - Event Storming for fun and profit
50mHow EventStorming Transformed Our Domain Modeling Process
40mEventStorming Lessons Learned - tens of thousands of post-its later
33mEvent Storming for Everyone
49mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process