Status update (week 7, 2019)

It’s February 15th, the second week since I started active development of AsyncAPI 2.0.0 and the 4th one since I started dedicating full-time to the initiative. Last two weeks come full of great stuff that will impact the future of the specification, the tooling, and the organization.

Latest changes in the specification

  1. Normalize topics as URI path templates. Starting on version 2.0.0, topics will have the form of a URI path template. For instance: “/user/{id}/changed”.
  2. Rename “topics” to “channels”: We want to remove confusing terms from the spec as much as possible. Some systems use topics, some use routing keys, event name, some… you know, there are many terms for the same thing. Therefore we chose to stick with a neutral one. Topics will now be channels.
  3. Remove the “events” section in favor of the root channel: Since channels will be URI paths, we can now safely map the root channel (“/”) to a “global channel” or “unique channel” for those systems that don’t support channels.

Organizational changes

  1. Welcome Mike Ralphson and raisel melian as AsyncAPI maintainers 🎉
  2. We now run AsyncAPI SIG (Special Interest Group) meetings every other week on the same day and time: Tuesdays at 6 PM CET. Find more information here.

Information organization changes

Have you seen our new README recently? It’s full of new stuff, including but not limited to:

  1. All specification versions. Including “next” what will eventually become 2.0.0.
  2. Information on how to join the meetings.
  3. Meetings calendar.
  4. Self-invitation link to our Slack workspace.
  5. And a list of our excellent contributors!

Next week

Planned work for next week is:

  1. Add support for multiple schemas: AsyncAPI 2.0.0 will support multiple message schemas, namely, JSON Schema 04–07, Protobuf, and Avro. We will keep supporting OpenAPI schemas.
  2. Improving connectivity milestone: This milestone addresses some issues related to server/broker connection.
  3. And last but not least, we’ll have our bi-weekly SIG meeting. Join us!

Until next week! 👋