Short answer: for a marketplace that accepts private uploads, treat a backup as a verifiable object plus a restore contract. Stream the database dump and archive to private object storage, record an immutable manifest, and issue short-lived presigned downloads only after authorization. The throughput decision is about multipart transfer and retry behavior, not about which dashboard has the nicest button.
Start with the restore contract
A cron job that creates a ZIP and gets a 200 response has not proved that the backup is usable. A restore needs an object key, byte length, checksum, creation time, schema version, and the list of included tenant or marketplace partitions. Keep that manifest beside the archive, and write a separate record in the application database so an operator can find the latest complete set without listing a bucket.
The private-upload path should have a different namespace from backups.…