As promised, we’re doing smaller and more frequent releases. So, it’s time for AsyncAPI 1.2.0! This version adds support for exciting new features, such as a way to document Streaming APIs and Event-based APIs, i.e., those that don’t have topics, e.g., the WebSockets ones.
Let’s go through all the new features of this release:
Streaming APIs and Event-based APIs
I’m very proud to announce the release of these features. Streaming API support, so far, goes for HTTP 1.1 chunked encoding and HTTP 2 server-sent events (SSE).
On the other hand, we have event-based APIs, e.g., WebSockets APIs. It solves the problem for those who implement APIs not using topics at all.
As an example, check the Gitter streaming API and Slack Real-Time Messaging API. Also, Kin Lane, the API evangelist, will be documenting lots of these APIs for the Streamdata.io catalog, so make sure you also follow him.
Avoiding parameters duplication
In the last release, we added support for topic parameters, however, if the same parameter was present in multiple topics, you had to duplicate the definition. That’s not ideal, so Mike Ralphson added support for components/parameters, where you can place the common definitions. Check out this example.
In the next release, we’ll be targeting two new features: message content-type and custom topic separators. Do you want me to notify you whenever there’s a new AsyncAPI release? Subscribe using the following form:
Until next time! 👋