Menu

Compare Cloud Storage Providers for Direct Browser Uploads — Node.js Retention Rules
📰

Compare Cloud Storage Providers for Direct Browser Uploads — Node.js Retention Rules

DEV Community: node·TitanJ53·41 minutes ago
#887SvAxF
#devtonodejs#devto#dev#upload#policy
Reading 0:00
15s threshold

Property management teams should choose browser-upload storage by its trust boundary and retention controls, not by whether its SDK can mint a presigned URL. For training artifacts, the browser should receive permission for one object, for a short window, with a server-owned key and a separately enforced retention policy. The storage provider matters after those rules are clear.

A useful design has three planes: a Node.js service authorizes an upload, the browser sends bytes directly to object storage, and a worker records completion and applies retention metadata. That separation keeps credentials out of the browser, but it does not make the browser trustworthy. It can still retry, abandon a multipart upload, or send an unexpected content type. I treat those as normal states, not exceptional ones.

Ownership decides the boundary.

No exceptions.

What is the real trust boundary for a training upload?

A presigned URL is a bearer capability.…

Continue reading — create a free account

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