Making Retries Safe with Idempotent APIs¶
Featonby, M. Making Retries Safe with Idempotent APIs. Amazon Builders' Library.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Dead-Letter Queue and Replay
- Replay without idempotency can double-process items and cause real damage: charging twice, shipping twice.
This sourceAmazon Builders' Library (n.d.). Idempotent handling makes retries safe by preventing a repeated mutating request from creating duplicate side effects.
- Replay without idempotency can double-process items and cause real damage: charging twice, shipping twice.
- Incident Backlog Cleanup
- Dedupe and revalidate. Merge the retry-storm duplicates and re-check what is still live, since disruptions manufacture copies and stale artifacts.
This sourceShows that retries after ambiguous failures can create duplicate resources and may require reconciliation to determine what is actually live.
- Dedupe and revalidate. Merge the retry-storm duplicates and re-check what is still live, since disruptions manufacture copies and stale artifacts.
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 2 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:b282e7863559 · see in the full table