Using dead-letter queues in Amazon SQS¶
Amazon Web Services. Using dead-letter queues in Amazon SQS.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Boundary-Case Quarantine
- It is the intersection's version of a dead-letter queue — the pattern of routing items that cannot be processed cleanly to a separate holding area instead of dropping or mis-processing them.
This sourceAmazon Web Services Documentation (n.d.). Describes dead-letter queues as isolating messages that were not processed successfully for later diagnosis or redrive.
- It is the intersection's version of a dead-letter queue — the pattern of routing items that cannot be processed cleanly to a separate holding area instead of dropping or mis-processing them.
- Dead-Letter Queue
- Its strength is converting three bad outcomes into one good one: instead of silent loss, infinite retry loops, or a poison message
This sourceAmazon SQS Developer Guide (nd). Uses a bounded receive count to move repeatedly unprocessed messages into a separate retained queue for isolation, diagnosis, and later redrive.
- Its strength is converting three bad outcomes into one good one: instead of silent loss, infinite retry loops, or a poison message
- Exception Queue Review
- Its strength is catching the semantic long tail no merge algebra can express, and creating accountability for conflicts that otherwise accrue with no owner — the archetype's "conflict counts grow without ownership" failure made someone's job.
This sourceAmazon Simple Queue Service Developer Guide (n.d.). Explains that a dead-letter queue isolates messages that could not be processed so they can be inspected, diagnosed, and redriven.
- Its strength is catching the semantic long tail no merge algebra can express, and creating accountability for conflicts that otherwise accrue with no owner — the archetype's "conflict counts grow without ownership" failure made someone's job.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:a75b6f4eda0c · see in the full table