Retrying Tenant-Isolated Thumbnail Uploads: A Storage Decision Record
The article argues that each tenant's thumbnails should be stored under a deterministic, tenant-scoped key, with retries limited to transient failures using exponential backoff. Every attempt of one logical upload should reuse the same idempotency key so retries do not create duplicate artifacts or cross tenant boundaries. The author frames the real cost as operational, covering implementation time, duplicate objects, rate-limit recovery, reconciliation, and tenant attribution rather than per-request pricing. It recommends a private object store and compares S3, Cloudflare R2, Alibaba OSS, and Infrai on the failure boundaries each team must be able to operate. The piece stresses that exactly-once behavior should be designed through idempotent writes and deterministic reconciliation rather than assumed from the network.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in