You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Documentation Related
There seem to be a few typos in this document regarding AsyncAPI.
If I'm understanding it correctly, you want to define the microservices using AsyncAPI. If that's the case, then subscribe and publish verbs must be exchanged in the following 4 places:
I know it can be confusing at first (and still is for me! 😅) but AsyncAPI operation verbs (publish and subscribe) represent operations the described application accepts instead of the operations it performs. So, for instance, when you say "publish" it means others can publish to this microservice (therefore the microservice should subscribe).
Needless to say, we're working on changing this for version 3 of the spec which we want to release this year. Here you can track progress regarding this publish/subscribe meaning: asyncapi/spec#520.
Happy to submit a PR :)
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
So having an offline chat with @tsurdilo, he rightly corrected my own confusion here 😅 It seems to be fine as it is because, for instance, the Online App Store is the one putting messages into store/order channel. Therefore the AsyncAPI verb should be "subscribe".
I'm closing the issue but feel free to reopen it again. Sorry for the noise 🙏
Search before asking
Documentation Related
There seem to be a few typos in this document regarding AsyncAPI.
If I'm understanding it correctly, you want to define the microservices using AsyncAPI. If that's the case, then
subscribe
andpublish
verbs must be exchanged in the following 4 places:I know it can be confusing at first (and still is for me! 😅) but AsyncAPI operation verbs (publish and subscribe) represent operations the described application accepts instead of the operations it performs. So, for instance, when you say "publish" it means others can publish to this microservice (therefore the microservice should subscribe).
Here's a good article explaining the meaning: https://www.asyncapi.com/blog/publish-subscribe-semantics
Needless to say, we're working on changing this for version 3 of the spec which we want to release this year. Here you can track progress regarding this publish/subscribe meaning: asyncapi/spec#520.
Happy to submit a PR :)
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: