tus.io VS CarrierWave

Resumable uploads are powered by the TUS protocol. The journey to get here was immensely rewarding, working closely with the TUS team. A big shoutout to the maintainers of the TUS protocol, @murderlon and @acconut, for their collaborative approach to open source. - Source: dev.to / 7 days ago

If it’s one way (that wasn’t quite clear from the requirements to me). Take a look at https://tus.io/. - Source: Hacker News / 4 months ago

HTTP/1 requests (uploads in this case) are also separate to some degree (though there are fairly stringent limits on connections per domain iirc which HTTP/2 resolves via the mentioned streams/multiplexing of connections). The problem they have specifically would be that in a single request (form post for example) those uploads will be linear. Solution really boils down to paralellizing the upload, using... - Source: Hacker News / almost 1 year ago

Hey hn, supabase ceo here This release introduces a few new features to Supabase Storage: Resumable Uploads , Quality Filters, Next.js support, and WebP support. As a reminder, Supabase Storage is for file storage, not to be confused with Postgres Storage. Resumable Uploads is the biggest update because it means that you can build more resilient apps: your users can continue uploading a file if their internet... - Source: Hacker News / about 1 year ago

If you're going to upload semi large files (100 MB) and want resumability for that upload (i.e. It can resume if the connection breaks down) I would recommend using https://tus.io and tusdotnet . It's an open protocol, clients exist for a large range of languages and tusdotnet supports customizing the storage to send files directly to Azure blob storage using Xtensible.TusDotNet.Azure. Source: about 1 year ago

We’re a Rails shop at Forem. In the Forem code base we use the CarrierWave gem to help with our file uploads. - Source: dev.to / about 2 years ago