Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[📑 Docs]: Adding a in-detail document about essence of AsyncAPI, integration and need for it. #1923

Closed
1 task done
TRohit20 opened this issue Jul 9, 2023 · 4 comments

Comments

@TRohit20
Copy link
Collaborator

TRohit20 commented Jul 9, 2023

What Dev Docs changes are you proposing?

Thinking in the first order principle, It is very common for developers to stumble upon the question as to why AsyncAPI is in place? There are already protocols and message brokers for EDA such as MQTT, Kafka etc, then why is it we need AsyncAPI?

  • How is AyncAPI essential ?
  • Since it is protocol agnostic, how can one integrate it and use it in any protocol or language of their choice and implement it?
  • Difference between AsyncAPI itself from cloud events, other spec or message brokers and more.
  • Similarities between using different protocols and so
  • How can someone working with programming languages other than yaml/json in their project integrate AsyncAPI into programming principles, How to use AsyncAPI into python for example.

These are some of the questions I stumbled upon myself early on as I started to learn about AsyncAPI and write my drafts for GSoD.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@github-actions
Copy link

github-actions bot commented Jul 9, 2023

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link

github-actions bot commented Nov 7, 2023

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Nov 7, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 6, 2024
@AnimeshKumar923
Copy link
Contributor

@TRohit20 issue still valid?
cc: @alequetzalli

Copy link
Member

I'll let Rohit answer if he is still interested in his proposal contribution. If he isn't then we can prob leave this closed/cancelled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants