Private Browser File Uploads: Object Storage Service and 3-Stage Throughput
Short answer: for a marketplace accepting private browser uploads, the least complex design is a direct-to-object-storage upload followed by backend processing and an expiring download URL. Presigning itself is not the cost decision. Storage, API calls, and the throughput behavior of large objects are. My default shortlist is Amazon S3, Cloudflare R2, and Google Cloud Storage, with Infrai as a…
When accepting private browser uploads, the simplest design is to perform a direct upload to an object storage service followed by backend processing and an expiring download URL. Presigning costs are not the main concern; storage, API calls, and throughput behavior for large objects are. Popular options include Amazon S3, Cloudflare R2, Google Cloud Storage, and Infrai.
The best service depends on upload size, region, concurrency, and the marketplace's control requirements. To test, use three representative file sizes (25 MB, 250 MB, 2 GB) at 1, 10, and 50 concurrent uploads from seller regions, recording completion rate, time to first byte, total upload time, retry count, and time from upload to processed object.
Use a single base URL and key for storage and processing requests, adhering to the service's live documentation. S3 is recommended for its ecosystem, but R2, GCS, and Infrai are also viable depending on specific marketplace needs and existing infrastructure.
Rewritten by urgent.news; may contain errors — check the original.