tusd VS OkHttp

If it’s one way (that wasn’t quite clear from the requirements to me).

take a look at https://tus.io/

We have an application tus - resumable file uploads we are deploying to Azure as an Azure App Service; a custom linux container. TusD exposes an endpoint /metrics that Prometheus is meant to scrape. Our App Service plan is set to rules-based scaling between 2 and 30 instances depending on load and traffic. The Azure Firewall is configured to not allow inbound connections to anything except via the load balancer (API management?).

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 protocols/standards like https://tus.io/ or S3-compatible APIs to push the data up then syncronize with a record/document on the server.

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 drops or if they accidentally close a browser tab

This implementation uses TUS[0], which is an open source protocol. We opted for this over s3's protocol to support the open source ecosystem. This means you can use several existing libraries and frameworks (like Uppy.js[1]) for multi-part uploads.

It also has some neat technical details, using Postgres Advisory Locks to solve concurrency issues.

The Storage team will be in the comments to cover any technical questions.

[0] TUS: https://tus.io/

[1] Uppy: https://uppy.io/docs/tus/

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

I'm a huge fan of https://tus.io/ because of the multiple backends and frontends

I usually use https://tus.io/ as the base protocol. Not too difficult to implement.

Have a look at https://tus.io the resumable file upload protocol.

We use https://tus.io/ to upload large files, but it's pure JS + ASP.NET, not through Blazor. You can easily do this in Blazor Server app, but it will have JS.

We will use Square’s Mock Webserver to spin up a mock server which we can use to simulate real api's request to the get coffee endpoint.

OkHttp Documentation

mockwebserver -> https://github.com/square/okhttp/tree/master/mockwebserver

I searched in the OkHttp GitHub project for an advice on which values may be suitable for Android apps nowadays but found no answers (only this old issue which does not help). Since we share a single OkHttp client Singleton for all our retrofit APIs and even Coil, I wonder if the default 5 maxRequestsPerHost is really enough.

You can technically add a Content-Length header for each part. It's not forbidden by the RFC, but nor is it common. It caused [problems](https://github.com/square/okhttp/issues/2138) for OkHttp, and they eventually removed it. Might be fine for internal-only use, though.

Boundaries are a lot like UUIDs, and rely on the same logic. When generating random data, once you have enough bits, the odds are against that sequence of bits ever having been generated before in the universe.

Lets be specific. This is the gradle build file for Squares okhttp client library. How exactly would your bld tool "predict" or "help" with all the parameters needed? There is no need to be defensive. Replace those large build files with your own, show where your approach is better and then understanding will lead to better solutions.

And adding to that: The asynchttpclient library is just a thin wrapper around OkHttp3, so it might be easier to just go with that instead: https://square.github.io/okhttp/

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

OkHttp