Streamlining EDA: AsyncAPI-Driven Design, Documentation, and Testing
summary
Shows how a design-to-runtime pipeline uses PSA+Event Portal for catalog, design, just‑in‑time provisioning and audit sync, exports to AsyncAPI documents, and runs code generation into real services (example repo: a coffee‑shop domain with five applications). Maps portal assets to AsyncAPI elements, adds KPIs for reuse, and demos Spring binding via spring Cloud stream so generated boilerplate ties directly to brokers; claims this cuts manual wiring and keeps design and runtime synchronized.
AI-written summary · about
chapters (16)
- 0:00AsyncAPI and event portals intro
- 1:55Event-driven architecture challenges
- 3:20Event portals vs architecture
- 4:24Solace PSA Plus Event Portal
- 6:08Event Portal personas and benefits
- 7:32Event Portal lifecycle phases
- 9:38Provisioning and deployment
- 10:44Security and audit features
- 11:47KPIs for event systems
- 12:10AsyncAPI for chaos testing
- 12:51Designing with AsyncAPI and Portal
- 14:17AsyncAPI and Portal roles
- 15:23Code generation with Spring Cloud Stream
- 17:47Coffee shop demo walkthrough
- 18:49Key takeaways
- 20:38Closing and resources
related talks
26mBridging the Gap between Design and Runtime in EDA with AsyncAPI and CI/CD
21mUsing the AsyncAPI Ecosystem for your Event-Driven Architecture
34mMaximizing the Value of Your Event Driven Architecture
42mAsyncAPI Recipes for EDA Gourmet
01h 03mOpenAPI and AsyncAPI, when to use which and why
28mStructure to Streams: Applying Full-Lifecycle API Management to ED Systems
39mEvent Design with AsyncAPI, DDD, and AI
31mAsyncAPI is here to stay