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

[Discussion/Question] why not use sqs visibility timeout to support re-queue rather than creating new messages #16

Open
chintan-synapse opened this issue Mar 3, 2022 · 0 comments
Open

[Discussion/Question] why not use sqs visibility timeout to support re-queue rather than creating new messages #16

chintan-synapse opened this issue Mar 3, 2022 · 0 comments

Comments

@chintan-synapse
Copy link

@Bogdanp I see you initially skipped implementation of re-queue to use SQS visibility timeout which sounds like a good idea but you later implemented the re-queue logic. Just want to know your thoughts behind this decision.
@chintan-synapse chintan-synapse changed the title [Discussion/Question] why not use sqs visibility timeout to support for re-queue rather than creating new messages [Discussion/Question] why not use sqs visibility timeout to support re-queue rather than creating new messages Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chintan-synapse