Event Design with AsyncAPI, DDD, and AI
summary
Claims that Domain Storytelling, Event Storming and Context Mapping plus LLM prompts can generate real AsyncAPI specs from workshop artifacts and that GitHub hosts working examples. Tools actually used include AsyncAPI YAML/JSON skeletons with Kafka bindings included and automated prompt-driven generation. Result is an 80% draft useful for one bounded context but quality falls as system complexity rises; generated specs need human semantic review and filling in examples and descriptions before deployment.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:47Synergistic Blueprint process
- 3:58Bounded contexts in DDD
- 7:11AsyncAPI and AI for APIs
- 11:07Domain storytelling
- 16:08Context maps and dependencies
- 19:44Event storming for processes
- 23:12AI limitations in designs
- 26:43AI for API generation
- 29:18Q&A
related talks
46mManaging Event Driven Architectures
21mUsing the AsyncAPI Ecosystem for your Event-Driven Architecture
26mBridging the Gap between Design and Runtime in EDA with AsyncAPI and CI/CD
31mSpecify Your Asynchronous APIs with AsyncAPI
42mAsyncAPI Recipes for EDA Gourmet
27mAsyncAPI & The future of API specs
21mStreamlining EDA: AsyncAPI-Driven Design, Documentation, and Testing
31mAsyncAPI is here to stay