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.

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

SQS "at-least-once" delivery #257

Closed
ifightcrime opened this issue Oct 13, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@ifightcrime
Copy link

commented Oct 13, 2016

Does shoryuken already handle locking, or do you have a recommended method for handling multiple deliveries? Thinking about pulling in something like redis-lock, but was hoping you might already have a suggestion or potentially solved this.

http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/DistributedQueues.html

@phstc

This comment has been minimized.

Copy link
Owner

commented Oct 14, 2016

Hey @ifightcrime there isn't a built in solution for that in Shoryuken.

I usually recommend:

You must design your applications to be idempotent (they must not be affected adversely when processing the same message more than once).

But I understand that it's something we can't achieve depending on the process. In case you strongly need that, I would say that a middleware and something like Redis would do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.