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

Why does Chore require memcached? #49

Closed
jellybob opened this issue Jun 12, 2018 · 3 comments
Closed

Why does Chore require memcached? #49

jellybob opened this issue Jun 12, 2018 · 3 comments

Comments

@jellybob
Copy link

The documentation mentions a dependency on Dali for SQS consumers, but doesn't mention what that is for. Is it possible to add a bit more explanation as to what that does, and would you be open to a PR replacing memcached with Redis, as I'd rather avoid introducing another piece of infrastructure to our system just for this.

@marcuswalser
Copy link

Hi @jellybob - because SQS's delivery guarantee is "at-least-once," we use memcached as a store for message IDs, so they can be deduplicated by the consumer processes. If your system is resilient to duplicate messages, you wouldn't require it and could safely omit it.

@marcuswalser
Copy link

Should have mentioned - we're happy to review a PR which adds Redis as an option for dedupe.

@jellybob
Copy link
Author

Thanks for the clarification - we always build in a way which can handle duplicates, so its not an issue for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants