[toomuchtodo]

I assume you're using Backblaze to host static assets you're rendering from your compute, and using Cloudflare to front and cache those static assets. You'd also use Backblaze for backups. Most network chatter would remain within your compute, and you'd want Redis, Mongo, Elastic, or Postgres as close to the compute (maybe k8s, maybe VMs, up to you) as possible, while shipping the snapshots to your object store. To your point about bandwidth costs, I recommend Backblaze and Cloudflare because they have an arrangement in that regard [1].

Reliably decouple whenever possible.

[1] https://www.cloudflare.com/bandwidth-alliance/ (Control-F "partners")

[jermaustin1]

For a couple of projects I use the b2/cloudflare "free bandwidth", but I have to pay egress from my droplet to b2 on user uploads, its well within the 1TB that you get for a $5 droplet, and smaller than a rounding error against my total bandwidth bucket of 9TB. So as I said, I'm fine.

[toomuchtodo]

Thanks for sharing your use case. I will submit a feature request with Backblaze to support request signing to support user uploads directly to the B2 object store, similar to what S3 supports [1].

[1] https://docs.aws.amazon.com/AmazonS3/latest/dev/PresignedUrl...