Skip to content

Update at_least_once_delivery.md #31

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.

Sign up for GitHub

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

Open
davidklempfner1 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update at_least_once_delivery.md #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _docs/at_least_once_delivery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ In case of failures that lead to message loss or take too long to recover from,
Sometimes, message duplicity can be coped with by the application using a [Message-oriented Middleware](/message_oriented_middleware/). Therefore, for scenarios where message duplicates are uncritical, it shall still be ensured that messages are received.

### Solution
For each message retrieved by a receiver an acknowledgement is sent back to the message sender. In case this acknowledgement is not received after a certain time frame, the message is resend.
For each message retrieved by a receiver an acknowledgement is sent back to the message sender. In case this acknowledgement is not received after a certain time frame, the message is resent.

![At-least-once Delivery]({{ "/sketches/at_least_once_delivery_sketch.png" | prepend: site.baseurl }})

Expand Down