Accelerating Event-driven Architecture with Domain-driven Design
summary
Claims that Domain‑Driven Design plus Event Storming turns fuzzy EDA planning into actionable boundaries by crowdsourcing events, sequencing them, and spotting pivotal events as boundary clues. Workshop toolkit is low tech: orange stickies for events, pink stickies for hotspots, swim lanes, read‑throughs and voting for business value. A one‑day session on a coffee ordering example yields emergent bounded contexts, a runnable event list, many clarified handoffs and still a handful of open questions to solve before implementation.
AI-written summary · about
chapters (11)
- 0:00Intro
- 2:29What is EDA?
- 15:32Event Storming
- 20:24Step 1: Audience
- 21:20Step 2: Events
- 24:05Step 3: Hot spots/questions
- 25:50Step 4: People
- 27:04Step 5: Pivotal events
- 28:17Step 6: External systems
- 36:23Discovering your bounded contexts
- 45:54Outro
related talks
55mNavigating complexity in event-driven architectures: A domain-driven approach
52mNavigating complexity in event-driven architectures: A domain-driven approach
42mDesign Principles for an Event-Driven Architecture
55mEvent Storming - how to shorten the distance between IT and Business
29mFrom Monolith to Cloud-Ready Microservice Architecture with DDD
39mEvent Design with AsyncAPI, DDD, and AI
42mApplication Architectures: The shadows and highlights of Event Driven Design
30mDomain-Driven Design + Command Query Responsibility Segregation + Event Sourcing