42 lines
1.8 KiB
JSON
42 lines
1.8 KiB
JSON
{
|
||
"sources": [
|
||
{
|
||
"id": "S1",
|
||
"title": "Timeouts, retries, and backoff with jitter",
|
||
"url": "https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/",
|
||
"publisher": "Amazon Web Services Builders’ Library",
|
||
"accessed": "2026-07-23",
|
||
"facts": [
|
||
"Retries can increase load on a dependency that is already failing.",
|
||
"Exponential backoff limits retry frequency, and jitter spreads retry timing across clients.",
|
||
"Retry behavior should be bounded rather than continuing indefinitely."
|
||
],
|
||
"notes": "Use for retry-load, backoff, jitter, and bounded-retry claims."
|
||
},
|
||
{
|
||
"id": "S2",
|
||
"title": "RFC 9110, HTTP Semantics — Idempotent Methods",
|
||
"url": "https://datatracker.ietf.org/doc/html/rfc9110#section-9.2.2",
|
||
"publisher": "IETF",
|
||
"accessed": "2026-07-23",
|
||
"facts": [
|
||
"A request method is idempotent when multiple identical requests have the same intended effect as one request.",
|
||
"A client can automatically retry an idempotent request after a communication failure before reading the response, subject to the specification's conditions."
|
||
],
|
||
"notes": "Use for the definition and retry implications of HTTP method idempotency."
|
||
},
|
||
{
|
||
"id": "S3",
|
||
"title": "Retry strategy",
|
||
"url": "https://cloud.google.com/storage/docs/retry-strategy",
|
||
"publisher": "Google Cloud",
|
||
"accessed": "2026-07-23",
|
||
"facts": [
|
||
"Retry behavior should consider whether the operation is idempotent.",
|
||
"Exponential backoff increases the delay between retry attempts and should use bounded limits."
|
||
],
|
||
"notes": "Use as a second implementation-oriented source for bounded backoff and idempotency checks."
|
||
}
|
||
]
|
||
}
|