This repository has been archived by the owner on Jan 3, 2025. It is now read-only.
Add dead letter queue to handle failed messages #687
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a DLQ that triggers after 4 failed attempts. Then a lambda function triggers from it, which checks if the user was still registered.
If the user is not registered something went really wrong and it sends a notification to sns (which triggers our slack lambda function? Not sure yet).
If the user is registered that means only something in the handling of the message went wrong, which we should investigate, but will not stop registrations from proceeding.
TODO: