Domain-Driven Design: A Complete Example
summary
Walks through a full DDD workflow: uses event storming (up to about 10 people can populate timelines) to expose events, picks bounded contexts (order, invoicing, delivery), and argues delivery is the core domain for this e‑commerce example. Recommends team topologies (stream‑aligned, enabling, platform, complicated‑subsystem) instead of heavy strategic design, shows tactical patterns (entities, value objects, aggregates, repositories, services) and mentions tooling (Structure101, x‑molecules). Builds a tiny email microservice on AWS Lambda to distribute slides; it works and locks addresses for 14 days.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:29Event storming basics
- 12:50Bounded contexts
- 20:20Core domain and strategy
- 24:10Team topologies
- 33:54Technical design
- 37:31Implementation considerations
- 45:26Conclusion and Q&A
related talks
01h 00mFrom Domain Driven Design DDD to Delivery
55mDomain-Driven Design: back to the roots
46mDomain Driven Design The Basics
38mWhat I talk about when I talk about Domain Driven design
44mStrategic Domain-Driven Design for dummies
59mDomain-Driven Design - Where Rubber Meets the Road
45mDon't Overdose on Domain-Driven Design
01h 02mDomain-Driven Design in ProductLand