AsyncAPI is a specification for defining message-driven APIs. We're on a mission to standardize message-based communication and increase interoperability of different systems.
AsyncAPI is an open-source community-driven project. We're happy to receive contributions from different people, no matter your skills or your area of expertise. There are many ways you can contribute to the project, not just code. There is always a need for: documentation, design, writing, evangelizing, code, issue triage, and more! We also welcome financial support and donations. Check out the contributing guidelines to learn more.
We're working hard to reach version 2.0.0, which will be full of great new features (and bug fixes.)
If you're looking for dates, check out our Milestones page.
➡️ [v2.0.0] Normalize topics and support multiple schemas
Before we continue heading to version 2.0.0, let's make the biggest breaking changes in the history of AsyncAPI: topic normalization and support for multiple schemas.
➡️ [v2.0.0] Improving connectivity
This milestone tackles the issues related to connecting to a server. These issues are very important to resolve for SDKs and code generators to work properly.
➡️ [v2.0.0] Improve user experience
This milestone is about improving developer/user experience for the specification and the tooling.
This milestone is about figuring out how to map protocols to AsyncAPI documents.
➡️ [v2.0.0] Augmentation ✅ Current milestone
This milestone is about creating mechanisms for the users to augment the AsyncAPI specification. We already have specification extensions, which provide a syntactical way to extend the spec. In this milestone, we should aim for providing the right mechanisms to extend the spec in different contexts and ways.
➡️ AsyncAPI version 2.0.0 Release Candidate launch
There's a new AsyncAPI version and now it's time for the tooling vendors to finish implementing it.
➡️ 🎉🎉🎉 AsyncAPI version 2.0.0 launch
Official launch of AsyncAPI 2.0.0! Party hard! 🍻
➡️ Backlog
The purpose of the backlog is to temporarily group issues that may be considered for the future. Please, note that it doesn't mean they will get implemented, however, there is a big chance.