Large File Browser Direct Upload: Multipart Presigned Parts and Retention
Short answer: for a large browser upload, send bytes directly to S3-compatible object storage with presigned multipart parts, but keep retention, deletion, and completion state in your application database; the upload is not finished until the server has made one explicit terminal decision. That's the trade-off I would put in front of an edtech platform team. Direct upload keeps the API out of…
We haven't written up this one. Dev.to has the full story — the link below goes straight to it.