Call for Votes: Choose protocols to document in the 2023 AsyncAPI Mentorship Program!

[Arya-Gupta]

As part of the AsyncAPI 2023 Mentorship Program, we are documenting how different protocols work with AsyncAPI. We need help from the community in selecting which protocols to prioritize for our project scope!

Vote from the following options:

1. WebSockets, Kafka
2. WebSockets, MQTT
3. Kafka, MQTT
4. WebSockets, Kafka, MQTT
5. Other

Your vote as a member of this community plays an important role in this decision. To vote, simply comment down below the option of your choice along with a short explanation.

This discussion will be closed after two weeks.

—

📢NOTE: The community vote for selecting popular protocol processes/tasks to accomplish with AsyncAPI is over here

cc: @asyncapi/tsc_members @alequetzalli @derberg @sergio

[kaushik-rishi]

How to vote @Arya-Gupta ?

[Arya-Gupta]

To vote, simply comment down below the option of your choice along with a short explanation.

[kaushik-rishi]

@Arya-Gupta thanks for updating the description. 🙂
Also looks like you've tagged the wrong Alejandra 😅

[Arya-Gupta]

Instructions for voting were already present, but thank you for bringing the incorrect tag to my notice!

[quetzalliwrites]

@Arya-Gupta thanks for updating the description. 🙂
Also looks like you've tagged the wrong Alejandra 😅

@Arya-Gupta Please remember to review your work and make sure you tag people correctly 🔥

[kaushik-rishi]

1. Websockets and Kafka

• one of each type
• I personally feel once you understand how Kafka works with AsyncAPI, you can easily get a hold of MQTT.

[jamesoyanna]

I suggest we prioritize WebSockets and Kafka - since our community mainly consists of web, mobile developers and data professionals.

WebSockets are well known for real-time communication in web and mobile applications & Kafka is well known in the data space. Also, there are readily available resources that can support documentation & mentorship.

[derberg]

Websockets and Kafka 💪🏼

[Amzani]

Websockets and Kafka

[akshatnema]

Websockets and Kafka

[dalelane]

Kafka and AMQP (Other)

I'm naturally biased towards choosing Kafka because I work with Kafka every day, but I do see a huge demand for Kafka in the companies that I work with, so that is my first choice.

I'm suggesting AMQP as a second protocol because I think we would also benefit from having something that isn't publish/subscribe. I think detailed documentation in how to do publish/subscribe would be invaluable, and we can get that from Kafka. But if we're going to document a second protocol in detail, I think we could get the most value from this by making it something as different as possible from Kafka (in model/usage/style - rather than just a different technology/wire protocol).

Choosing something like AMQP could enable us to demonstrate how to use AsyncAPI to document request-reply or point-to-point messaging patterns, and show how AsyncAPI isn't solely for describing publish/subscribe architectures.

[CynthiaPeter]

Hello @dalelane,

This input is super helpful and will also help us in this discussion. Please take some time to share some specific topic suggestions in this discussion. Thank you

[AceTheCreator]

Kafka and AMQP

[KhudaDad414]

Kafka, MQTT

[Shurtu-gal]

Websockets and Kafka as MQTT is easier to pick up after that and furthermore, these are the most used ones.

[SumantxD]

MQTT, as i'm using it in currently 😺

[Arya-Gupta]

The most voted protocols are:

WebSockets - 6
Kafka - 9
MQTT - 2
AMQP - 2

This discussion has now been closed.

[smoya]

Kafka, Websockets, and AMQP.