2nd half of 2021 at AsyncAPI

Lukasz Gornicki

Lukasz Gornicki

ยท8 min read

Around August, I communicated that because vacation is a dead season (in Poland we call it cucumber time) I will not do my monthly updates or write a single vacation summary.

Well, the thing is that vacations were not as quiet as I expected. In September, a carousel started that was impossible to stop.

I started writing status updates bi-weekly in early 2020. These were about simple improvements in specific libraries, very detailed on libraries release level. Back then, I basically knew every single new thing happening in the initiative. This year I switched to monthly updates as there was simply too much happening, and I could not really do those bi-weekly. I also started picking the most important news as there were too many things happening.

I submit my official apologies to those awaiting my update-related articles. Honestly, looking at the size of the community and the growth that we are noticing, I don't know how I'll manage to publish these regularly in 2022. Maybe we should start writing those as a collective.

What I can promise for sure is that in January 2022, I will write a summary article about AsyncAPI growth in 2021.

More regular live-streams

We started two live streams under the AsyncAPI brand:

  • Thinking Out Loud is hosted by AsyncAPI Founder (Fran Mendez). He invites different community members to talk about AsyncAPI specification. All recordings are available in the official YouTube playlist. Fran plans to continue doing them in 2022 as well.
  • Contributor-first is strictly targeted at new or existing contributors. Any AsyncAPI Technical Steering Committee member can volunteer as a host and talk about specific contribution-related topics. We aim to have it as frequently as possible, at least once a week. All recordings are available in the official YouTube playlist. Based on the community feedback, the live stream will be renamed to Let's talk about contributing in 2022.

Hosting these live streams is all possible thanks to the great support from the Restream.io folks who gave us free access to the tool that enables us to live stream directly to all our social media channels.

All official meetings are always listed in our:

The best way to learn about a new event is to join our official Google Group that we use as a mailing list for invites.

Solving publish/subscribe confusion aka possible AsyncAPI 3.0 release in 2022

It was hard to find someone in the community that was not confused by the semantics related to the publish and subscribe operations when learning about the AsyncAPI specification. Many people were asking in Slack. People were also opening pull requests to fix our documentation, assuming we mixed things up by accident.

There are cases where education is not enough. You can have great docs and education materials. Still, some stuff just needs to be improved and cannot be fixed by documentation.

At the beginning of my tech career, I learned a sentence from an experienced developer: "documented bugs become features". Sometimes you do not have a chance to learn from the best ๐Ÿ˜…

This is causing too much confusion and needs to be solved in 2022. It is probably not possible without a breaking change in the specification.

Please join us and help us improve not only the specification but also update the tooling:

Google Summer of Code Summary

We closed holidays 2021 with massive success of the Google Summer of Code participants. All participants not only finished their projects, but they also became members of AsyncAPI Technical Steering Committee and also got a chance to present their work at the 2021 AsyncAPI Conference.

It was a pleasure to work with these folks and see them staying with us after GSoC ends. I, therefore proposed we do it again in 2022 on a larger scale.

Technical Steering Committee members setup

After joining the Linux Foundation (LF) and applying the open governance model, it was time for us to start setting up a Technical Steering Committee (TSC).

So here we are, 9 months after joining LF, we already have 24 members. Check out the complete list of all the TSC members. Pay attention to those that are marked as Available for hire. Don't let folks work for free. Pay them to work on open-source. Be good humans.

Do you want to be on that list? Watch the following ๐Ÿ‘‡ presentation.

There are many things still missing, such as a TSC list synchronization, voting process automation, and more. Other things still need a lot of work. If you want to contribute to the project and you are a fan of automation, this is the right topic to help with.

Welcome Studio and Goodbye Playground

We released a new application that you can use to work on your AsyncAPI files.

Before, you could use the AsyncAPI Playground, but now we are redirecting traffic to a new, beautiful ๐Ÿ‘‰ AsyncAPI Studio ๐Ÿ‘ˆ

The new Studio has a bright future, and you should expect lots of new features coming there. I definitely recommend checking out Studio's GitHub repository.

The cool stuff is that it is also integrated with the AsyncAPI CLI:

1#install CLI
2npm install -g @asyncapi/cli
3#create new file using an example
4asyncapi new --file-name=asyncapi.yml --example=default-example.yaml --no-tty
5#start studio that picks up asyncapi.yml file from the context it runs in
6asyncapi start studio

Repository with Playground source code will most probably be archived and moved to organization with old archived projects.

Hackathon

This year, we hosted our first AsyncAPI Hackathon. Even though we did not have a dedicated marketing campaign, and even though AsyncAPI is not trivial and requires experience to build tools for it, we received 9 submissions.

Souvik De won first prize with AsyncAPI Bundler. Check out Souvik talking about the AsyncAPI Bundler at AsyncAPI Conference.

We also had 2 folks that tied in 2nd place:

Congrats to all of you folks!

Check out this discussion to get more details on the Hackathon voting process.

P.S. During the Hackathon, we also had a lot of people engaging with us because of Hacktoberfest. We got 30 issues resolved and merged.

Conference

COVID-19 is still here. Thus, we decided to host the 2021 AsyncAPI Conference this year only in online mode. It was a three-day event with lots of great content, and most importantly, with the 1st day dedicated to contributors only.

The conference was live-streamed. Full-day recordings were released immediately, and individual talk recordings will follow. All will be listed under the dedicated Conference playlist.

Check out the current sum of people that watched it during the conference and after as recordings:

  • Day 1:

    • YouTube: 1119
    • Twitch: 89 (during event only, later Twitch removes old videos)
    • LinkedIn: 148
    • Twitter: 692

    Total: 2048

  • Day 2:

    • YouTube: 737
    • Twitch: 56 (during event only, later Twitch removes old videos)
    • LinkedIn: 49
    • Twitter: 283

    Total: 1125

  • Day 3:

    • YouTube: 521
    • Twitch: 26 (during event only, later Twitch removes old videos)
    • LinkedIn: 29
    • Twitter: 312

    Total: 888

These numbers are great if we compare them against a total of 600 registrations!

Personally, the best number that I discovered was when I started listing the names of all the people who helped during the hackathon and conference organization. I think 62 is now my favorite number โค๏ธ

Picture showing names of all people that helped in event organization.

Picture showing names of all people that helped in event organization.

What about 2022? People during the conference voted for a hybrid approach:

Picture showing that out of 25 voters, 18 (72%) voted for a hybrid conference that is both online and in-person.

Picture showing that out of 25 voters, 18 (72%) voted for a hybrid conference that is both online and in-person.

Join related discussion and help organize it.

Photo by Ian Schneider on Unsplash