Add support for retries, backpressure, and at-most-once, at-least-once, and exactly-once semantics

[fmvilas]

Reason/Context

There are many points in the existing codebase that can lead to lost messages.

Description

We should review and identify which parts of the codebase can cause problems and fix them. We should be looking for:

1. Retries. What if calling a function fails? Especially when we implement the HTTP runtime. We should be retrying and letting the user configure how to do it.
2. Backpressure. What happens if a client/broker starts sending too many messages too quickly? We should be able to control the number of messages per second we want to receive, telling the client/broker to slow down. This is not always possible but definitely should be implemented for those protocols that provide a mechanism for that.
3. At-most-once, at-least-once, and exactly-once semantics. We should be able to guarantee that a message is going to be received either at most once, at least once, or exactly once. Some protocols don't have a mechanism for that so we should focus on those that have it.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 60 days if no further activity occurs. To unstale this issue, add a comment with detailed explanation.
Thank you for your contributions ❤️

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

[fmvilas]

Dear bot, keep this issue open because we still need to work on it.

[sudoshreyansh]

Hi, I would like to work on this as a part of the mentorship program, if it gets selected.

[abhishek-iiit]

Hi @fmvilas, I would love to contribute to this Project under AsyncAPI Mentorship. I did gone through the issue and I believe under your/mentor guidance and support, I can be able to make it and lead it to a success.

Looking forward and making out plans to execute to this project :)

[fmvilas]

Congratulations @sudoshreyansh for being selected for the AsyncAPI Mentorship program to work on this issue 🎉

[sudoshreyansh]

Thanks @fmvilas !

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

[fmvilas]

Dear bot, don't mark it as stale, it's in the works right now.

[KhudaDad414]

@sudoshreyansh Hey mate, does #323 resolves this issues? 🤔

[fmvilas]

No, it doesn't. #323 is definitely a step forward but this issue should go beyond MQTT.

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