AsyncAPI and DDD - A Pretty Couple
summary
Combines Domain-Driven Design practices with AsyncAPI to produce concrete event contracts: a freelance task-management example yields task created / task done events propagated to inbox and invoicing, with synchronous user lookups and Kafka-style channels. Workshops use domain storytelling → event storming → context map → visual glossary to find aggregates, commands, events and payload fields. A skeleton YAML plus LLMs (Cloudy and ChatGPT) generates AsyncAPI specs quickly but needs manual additions for descriptions and examples; overall the approach produces usable event APIs.
AI-written summary · about
chapters (11)
- 0:00AsyncAPI and DDD intro
- 1:28DDD overview and business canvas
- 7:13Domain storytelling
- 8:40Event storming
- 13:15Context map design
- 16:50Ubiquitous language glossary
- 18:58AsyncAPI basics
- 21:27AsyncAPI operations and events
- 23:40AsyncAPI channels and payloads
- 27:19AI-generated AsyncAPI specs
- 31:38Conclusion: AsyncAPI and DDD
related talks
47mDomain-Driven Design: A Complete Example
26mDefining Event Modeled systems with AsyncAPI
45mThose API Calls Could Have Been a JOIN!!
42mHigh-Speed DDD (revisited)
28mCode Generation For Enterprise Integration Patterns w/ AsyncAPI & ZenWave SDK
20mRevolutionizing API Management: Insights from an Architect
30mDomain-Driven Design + Command Query Responsibility Segregation + Event Sourcing
01h 00mFrom Domain Driven Design DDD to Delivery