From Side Project to Industry Standard: Story of AsyncAPI
summary
AsyncAPI claims a community-built spec that reached a $33M valuation and CNCF backing, solves “contract blindness” by describing producers, channels, messages and protocols, and is used by LEGO, eBay and major banks to improve handoffs and manage Kafka topics. The ecosystem includes a generator that generates code from message formats (Java + Quarkus template demo), CI/CD validation to catch schema breaks, a docs studio that acts as a single source of truth, sponsorships and active GSOC/mentorship programs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Event-driven architecture matters
- 4:41Challenges in event-driven systems
- 8:58AsyncAPI core principles
- 13:57Why AsyncAPI succeeded
- 17:13AsyncAPI ecosystem
- 21:29AsyncAPI code generation demo
- 24:38AsyncAPI adoption and use cases
- 26:47AsyncAPI career boost
- 28:56Q&A
related talks
23mHow Companies Actually Use AsyncAPI
22mAsync API Specification 2.0
27mThe State of AsyncAPI
23mBroadening the API Landscape: AsyncAPI and CloudEvents in the Enterprise
39mIntroduction to AsyncAPI for Apache Kafka
08mMy Journey from Contributor to a TSC Member at AsyncAPI
21mUsing the AsyncAPI Ecosystem for your Event-Driven Architecture
08mSimple Ways to Get Your Organization to Adopt AsyncAPI