Node.js Presigned URLs Offer Private Storage for Large Export Files
The article argues that large exports should stay in private object storage, with browsers receiving short-lived presigned GET URLs only once the file is complete. It recommends giving each export attempt a unique object key and tying access checks to both job ownership and job state. Streaming writes and multipart uploads are suggested to keep memory use bounded for multi-gigabyte files. The author also warns that URL expiry and object deletion run on separate clocks, so cleanup should be idempotent and tracked with a delete_at timestamp. Testing with multiple tenants, expired links, and duplicate deliveries is recommended to catch access and lifecycle bugs early.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in