Supabase Storage now supports the S3 protocol • Hacker News Board

Re: Supabase Storage now supports the S3 protocol

#191

Post by kiwicopple » Mon, Apr 22, 2024, 4:31 AM UTC

masfuerte wrote: post #106

kiwicopple wrote: post #31

Earlier quoted context omitted.

It's more of a "accessibility layer" on top of S3 or any other s3-compatible backend (which means that it also works with MinIO out-of-the-box [0]) I don't think we'll ever build the underlying storage layer. I'm a big fan of what the Tigris[1] team have built if you're looking for other good s3 alternatives [0] https://github.com/supabase/storage/blob/master/docker-compo... [1] Tigris: https://tigrisdata.com

I'm still confused. Who is paying Amazon? Is it 1. You buy the storage from Amazon so I pay you and don't interact with Amazon at all or 2. I buy storage from Amazon and you provide managed access to it?

it's 1 - you pay us, we pay AWS.

In the future we will likely provide "bring your own s3" (2)

Re: Supabase Storage now supports the S3 protocol

#192

Post by Havoc » Mon, Apr 22, 2024, 8:39 AM UTC

kiwicopple wrote: post #188

Havoc wrote: post #156

What are the chances of Supabase doing a license change? Seems to be fashionable these days so always a little wary of building on these sort of platforms

Unfortunately there isn't a way to prove our intentions to remain open source That said, I think Supabase is much more de-risked from this happening because we aim to support existing tools with a strong preference of tools that are controlled by foundations rather than commercial entities. For example, 2 of the main tools: - Postgres (PostgreSQL license) - PostgREST (MIT license) Every tool/library/extension that we…

Thanks for the response. Seems reasonable

Re: Supabase Storage now supports the S3 protocol

#193

Post by _boffin_ » Mon, Apr 22, 2024, 3:35 PM UTC

iamcreasy wrote: post #184

vbezhenar wrote: post #146

Earlier quoted context omitted.

I don't. S3-compatible storages usually are significantly cheaper, allow to offload HTTP requests. Also huge databases make backups and recoveries slow. The only upside of storing blobs in the database is transactional semantics. Buf if you're fine with some theoretical trash in S3, that's trivially implemented with proper ordering.

What do you mean by transactional semantics?

ACID, I presume

Re: Supabase Storage now supports the S3 protocol

#194

Post by iamcreasy » Tue, Apr 23, 2024, 5:15 AM UTC

Rapzid wrote: post #186

iamcreasy wrote: post #185

Earlier quoted context omitted.

I am confused and curious. Can you please elaborate on how streaming is related to pg storage?

If you can't stream data the user is sending through the server to the database you have to buffer the entire payload in memory. This doesn't scale well but can work for smaller payloads. You CAN stream bytea but: * Good luck finding a client that supports it(npgsql does actually) * It doesn't support support start the read/write at any location other than the start. So you'd have to basically build the Lob(Large Obj…

What kind of streaming from user are we talking about? User interaction, such as mouse move, clicks?

Does each interaction essentially create a SQL update statement? And are you trying to avoid buffering those statements?