Knowledge documents in Network.
Assuming a queue may deliver the same message more than once, this explains how to ack only on success, block duplicate execution with an idempotency key, and report when redelivery is exhausted
A pattern that puts a queue and a worker in front of a slow or one-at-a-time external system, so requests are accepted immediately and processed at the system's own pace, along with how to design acks, fallbacks, and retries
How to widen the interval (backoff) and mix in randomness (jitter) when retrying transient failures, so retries do not turn into a storm that hammers the other side again, plus the criteria for choosing which errors to retry
A rewrite is a proxy, not a redirect, so it passes upstream 3xx responses straight through — why pointing one at an origin that canonicalizes creates an infinite loop, and how to fix it
The negotiation cache that uses ETag and If-None-Match to serve unchanged responses as 304, driving download bytes to zero. Covers the limit of saving only bandwidth (not server compute) and the cheap validator
Cache key normalization when storing temporary signed URLs: strip auth queries only, keep semantic queries
How to block SSRF with a scheme/host allowlist in a proxy where the server fetches a user-supplied URL
How the client uploads a binary directly to object storage using a one-time URL signed by the backend, and the step-by-step contract