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.

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

Jump to bottom

Specify where "transactions" should happen. #25

Open
Kuinox opened this issue Jan 17, 2021 · 0 comments
Open

Specify where "transactions" should happen. #25

Kuinox opened this issue Jan 17, 2021 · 0 comments
Labels
enhancement New feature or request resilience

Comments

@Kuinox
Copy link
Member

Kuinox commented Jan 17, 2021 •
edited
Loading

Currently we don't specify any transactionality;
There is no secure way to execute code after a message was ack for example.
Currently on receiving an ACK we:

  • Destroy any information about this message
  • Resolve the task that the user may be awaiting with the result.

It mean that if something happen between these step, the user won't be aware of the response.
@Kuinox Kuinox added resilience enhancement New feature or request labels Jan 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request resilience
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Kuinox