Menu

Processing Image Thumbnails: Upload Times Before Object Storage in Go, Explained
📰

Processing Image Thumbnails: Upload Times Before Object Storage in Go, Explained

DEV Community: go·eliasfischer8351·7 days ago
#t9sQ4jlG
#devtogo#devto#dev#tenant#storage
Reading 0:00
15s threshold

Short answer: when thumbnail processing times out before an object-storage upload, separate image work from the storage request, measure each stage, and upload only completed bytes under a tenant-derived key. For a fintech export, the application must own authorization, audit state, and retry semantics; storage is the byte boundary, not the tenant policy.

The least complex design is a bounded worker: decode and resize, record the processing time, encode the result, then upload it with a deadline that does not include unrelated image work. Large source files and inefficient resizing operations can consume that deadline before the PUT begins. A storage provider change cannot repair a slow decoder.

For example, a destination such as tenant/acme/thumbs/payment-123.webp makes the intended partition visible, but a prefix is not an authorization decision. The authenticated tenant must be checked before the path is built, and the database should relate the source object, derived thumbnail, and export request.…

Continue reading — create a free account

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