Menu

How to Retry 3 Tenant-Isolated Thumbnail Uploads — A Storage Decision Record
📰

How to Retry 3 Tenant-Isolated Thumbnail Uploads — A Storage Decision Record

DEV Community: go·ArthurFinley2291·4 days ago
#Vi2IvcAJ
#devtogo#devto#dev#tenant#storage
Reading 0:00
15s threshold

Short answer: put each tenant's thumbnail under a deterministic tenant-scoped key, retry only transient failures with exponential backoff, and make every attempt carry the same idempotency key. This is the right boundary for a gaming image-resizing pipeline because a retry should repair a transport failure without creating a second artifact or crossing tenants.

The useful unit of analysis is not the storage request's unit price. It is the operating bill: implementation time, duplicate objects, rate-limit recovery, reconciliation work, and the cost of proving which thumbnail belongs to which tenant. I would start with a private object store and a small retrying writer, then choose among S3-compatible services, Cloudflare R2, Alibaba OSS, and an API surface such as Infrai according to the failure boundary the team can actually operate.

Decision Record: What Must Remain True

The system stores training artifacts produced while resizing game images.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.