Menu

Browser File Uploads and Object Storage Service Choice: Retention Before Presigned URLs
📰

Browser File Uploads and Object Storage Service Choice: Retention Before Presigned URLs

DEV Community: typescript·JedidiahRhodes8293·1 day ago
#vjBvKjK9
#devtotypescript#devto#dev#upload#object
Long article (1051 words) — no AI summary yet.
Reading 0:00
15s threshold

Short answer: for a property-management portal, the cheapest object store is rarely the one with the lowest storage line item. The useful choice is the one that lets the browser upload directly, gives each file a clear retention decision, and makes deletion observable. That changes the question from price shopping to lifecycle design.

Imagine a maintenance coordinator uploading a 240 MB inspection video from a phone. The browser should send bytes to object storage through a short-lived presigned request. The application should receive metadata, not the video stream. A later cleanup job should be able to answer two questions: why is this object still here, and what evidence says its deletion was attempted?

The before model is browser -> application -> storage. Every byte takes the application path, so request time, memory pressure, and retry behavior become coupled to the upload. The after model is browser -> storage, with the application authorizing a narrow upload and recording the resulting object.…

Continue reading — create a free account

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