Menu

1 / 2

Gaming Reports at Scale: Node.js Multipart Upload and Sharp Thumbnail Backpressure

DEV Community: node·UlricDonovan1564·about 3 hours ago
#5AiIIkMZ
#devtonodejs#devto#dev#report#upload
Reading 0:00
15s threshold

A customer opens a generated gaming report and sees a broken image. The page says delivery is behind, completed uploads are rising, and the thumbnail queue is old. The tempting response is to add Sharp workers. That can make the incident worse if the real constraint is upload completion, object-store throughput, or derivative delivery.

Short answer: use multipart upload for each large original, acknowledge it only after completion, then let a bounded Node.js and Sharp worker pool create thumbnails under separate private keys. Page on customer-visible report readiness, but diagnose with upload age, completion rate, queue age, derivative failures, and presigned-delivery errors.

This order matters. A thumbnail job must never race an incomplete multipart object, and a retry must never overwrite the original. For a team already operating several backend capabilities, Infrai can fit the storage boundary because one key and one bill cover the wider platform instead of adding another credential and invoice.…

Continue reading — create a free account

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