Marketplace Cloud Object Storage for User Avatar Uploads: Private API Access
Short answer: Choose private object storage with a server API and presigned reads, then make retention a testable policy instead of a bucket setting you trust by inspection. For a marketplace storing seller training artifacts, access control comes first; delivery simplicity is the deciding tie-breaker. The concrete fixture is small: a 2 MB avatar, a 40 MB training PDF, and a duplicate key that…
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.
This story
This is one outlet's version. Read the fullest account.