Problem we need to fix

When uploading very large files (GB and more), requiring that the file's content is added to the request (as base64 for REST, or multipart/form-data for GraphQL) is a problem. The file will be written to disk, and will use a lot of server disk space, or worse, be read into memory.

Approach

One way to improve that would be to add an input URI parameter to both REST and GraphQL. It would be used to copy the file to its destination while minimizing the amount of used resources.

Story expectation

large files can be uploaded using REST and GraphQL, by providing a remote URI, without specific tweaks to the server's settings (memory limit, max post size...)

DAM notes

A proper DAM integration would be an alternative to this: the DAM would take care of the heavy lifting, and we would only be storing a reference to the large item.