AsyncAPI as a Driver of the SDLC
summary
AsyncAPI files drive the SDLC by generating code, importing into an Event Portal, and triggering deployment via Postman → Jenkins → Ansible Tower; a CLI importer updates versions and an IntelliJ code‑generation endpoint produces runnable packages. Demos show async API bindings (Solace, Kafka) mapped from logical server groups to physical brokers, Ansible playbooks creating queues/topics automatically, and versions tracked semantically — the pipeline works end‑to‑end in the demos and reduces bespoke config and brittle custom scripts.
AI-written summary · about
chapters (10)
- 0:00AsyncAPI and SDLC
- 3:58AsyncAPI goals in SDLC
- 6:47Challenges without AsyncAPI
- 9:37AsyncAPI standardizes SDLC
- 11:26AsyncAPI in SDLC workflow
- 12:09IntelliJ code generation demo
- 15:48AsyncAPI challenges and future
- 17:15AsyncAPI catalog and governance
- 20:10Ansible infrastructure deployment demo
- 22:39Conclusion
related talks
26mBridging the Gap between Design and Runtime in EDA with AsyncAPI and CI/CD
23mHow Companies Actually Use AsyncAPI
28mEvent Driven API Management - Increase Reusability with AsyncAPI
39mIntroduction to AsyncAPI for Apache Kafka
08mSimple Ways to Get Your Organization to Adopt AsyncAPI
08h 51mAsyncAPI Conference 2021 - Day 3
08mUntangling your production events with the asyncAPI discovery tool
32mFrom Design to Code using AsyncAPI