Read April 2021 at AsyncAPI for the update from April.
JSON Schemas for the bindings
AsyncAPI is protocol agnostic. It doesn't mean that you cannot specify some protocol-specific information in the AsyncAPI document. It is possible through a bindings feature. In different parts of the AsyncAPI document, you can provide specific details for Kafka, MQTT, and other protocols. Definitions of bindings are maintained separately from the main AsyncAPI specification in the bindings repository.
The current challenge with bindings is that they are hard to validate because they are written in Markdown, human-readable form only. Support in tooling is also pretty limited because of this. We had to start maintaining the JSON Schema, as we do with the main AsyncAPI specification.
Thanks to a monumental effort from Khuda Dad Nomani I'm proud to say that all 15 bindings now have their JSON Schemas. So for example Kafka binding has its JSON Schemas. The next step is to figure how to link these JSON Schemas with the main AsyncAPI specification JSON Schema and support it in parsers.
For more details, have a look at this issue and help us out to drive it further.
Bindings are getting more and more adoption and interest. Many interesting discussions are happening that are shaping the bindings feature. I highly recommend joining them, like, for example, the debate started by Ian Cooper to get consistency between protocol configurations using bindings.
InfoQ Architecture and Design 2021
Assigning channels to servers
I want to suggest you pay attention to the proposal from Gerald Loeffler that introduces a way to assign a channel to a specific server. This proposal would enable you to have a single AsyncAPI document with multiple different servers supporting different protocols. You could specify that your application is subscribed to channel A on the Kafka server and that it publishes messages to Channel B on the MQTT server.
It is a feature that many asked for in the past. Please jump into the discussion. Even if you have no comments, then at least leave some emoji, so we know it was viewed and what people have an opinion.
Iván García Sainz-Aja donated to AsyncAPI Initiative the plugin he developed for the VSCode to enable you to preview AsyncAPI documents using our HTML template directly in the IDE. We need to do some cleanup and rebranding now, and then we will be ready with further development.
Any help will be highly appreciated, so please check out the repository.
New AsyncAPI-related tools
We have new tools on our list of tools created by the AsyncAPI Community:
- EventBridge Atlas from David Boyne
It parses AWS EventBridge schemas into documentation solutions, shows rules matched to your events, adds metadata to each event property, support slate, AsyncAPI, and docuowl output, and more...
- Asynction from Dimitrios Dedoussis
The purpose of Asynction is to empower a specification first approach when developing SocketIO APIs in Python
Tests coverage tracking in tooling
Jonas Lagoni that actively maintains the library gave Coveralls a score of 8 out of 10. Now we need to roll it out to other projects. If you were looking for some good first issue to start contributing to AsyncAPI, then this issue is a good one.
Modelina is a data models generator that supports AsyncAPI and JSON Schema. Its goal is to make it easier to write code generators. Jonas released many improvements in May and still does, so it is best to try it out now and provide feedback.
We are growing fast, and it was the right time to do some reorg in our Slack workspace to get some structure, clean up, and properly structure discussions. In the end, yes, we are still using Slack because we got accepted as an exceptional organization and received Standard
All the official Slack channels are listed below:
I think that actually, the most important thing is that we defined our first version of the Slack etiquette.