Another concept document talking about operations and action

[derberg]

Reason/Context

This issue is a result of asyncapi/spec#934 (review)

In the past people had hard time understanding what publish and subscribe means -> https://www.asyncapi.com/blog/publish-subscribe-semantics

So we changed to send and receive.

It definitely makes sense to address different concepts of naming:

• publish & subscribe
• produce & consume
• and now we have send and receive

Reason is simple, we just had to pick something generic, like in case of channels we had alternatives like queues or topics but channels was selected 🤷🏼

some more info in asyncapi/spec#618 (just search for mention of send or receive)

Description

yeah, I think we should have a document under Concepts where we have other concepts explanation. Maybe we just need to update existing docs about Producers and Consumers 🤔

[derberg]

cc @alequetzalli @smoya

[github-actions]

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 ❤️