From Side Project To Industry Standard
summary
AsyncAPI starts as a personal side project to describe event-driven systems (first used with RabbitMQ), grows into a spec plus documentation and code generators, and gets adopted by Slack before any governance is set. Growth forces cleanup: a 10‑person team forms, work moves onto GitHub and Slack, and the project is donated to the Linux Foundation with 40+ technical steering committee members today. The project proves it can scale tooling, survives creator burnout, and even helps evacuate two contributors from Afghanistan.
AI-written summary · about
chapters (10)
- 0:00Conference welcome
- 1:13Side project to opportunity
- 6:19AsyncAPI spec vision
- 10:23Burnout and validation
- 15:41Salesforce offer
- 21:49Rejecting offer and governance
- 26:50Linux Foundation and growth
- 31:29Three key takeaways
- 41:05Project challenges and vision
- 46:25How to contribute
related talks
51mAsyncAPI: from personal project to industry standard
13mEverything You Wish To Know About The AsyncAPI Community
25mThe State of AsyncAPI Initiative
23mHow Companies Actually Use AsyncAPI
22mHow Contributing to AsyncAPI Tools Inspired a Career in OSS
26mPast, Present, and Future of AsyncAPI
29mState of AsyncAPI Community
08mMy Journey from Contributor to a TSC Member at AsyncAPI