121–130 of 194 posts
Always thought it’s kind of odd how the proprietary API of AWS S3 became sort of the de-facto industry standard
S3 is one of the original AWS services (SQS predates it), and has been around for 18 years. The idea of a propriety API becoming the industry defacto standard isn't uncommon. The same thing happened with Microsoft's XMLHttpRequest.
Earlier quoted context omitted.
This is my biggest reservation towards Supabase. Google bought Firebase in 2014. I've seen Vercel run Nextjs in to the ground and fuck up their pricing for some short-term gains. And Figma almost got bought by Adobe. I have a hard time trusting products with heavy VC backing.
You know the whole point of YC companies is to flip their equity on the public market right and then moving on to the next one?
Dear supabase. Please don’t get bought out by anyone and ruined. I’ve built too many websites with a supabase backend now to go back.
This is my biggest reservation towards Supabase. Google bought Firebase in 2014. I've seen Vercel run Nextjs in to the ground and fuck up their pricing for some short-term gains. And Figma almost got bought by Adobe. I have a hard time trusting products with heavy VC backing.
Can Supabase host static content yet (in a decent way)?
We don’t support static website hosting just yet - might happen in the future :)
I like to Lob my BLOBs into PG's storage. You need that 1-2TB of RDS storage for the IOPS anyway; might as well fill it up. Large object crew, who's with me?!
I like to Lob my BLOBs into PG's storage. You need that 1-2TB of RDS storage for the IOPS anyway; might as well fill it up. Large object crew, who's with me?!
38TB of large objects stored in Postgres right here
The client I use currently, npgsql, supports proper streaming so I've created a FS->BLOB->PG storage abstraction. Streamy, dreamy goodness. McStreamy.
I like to Lob my BLOBs into PG's storage. You need that 1-2TB of RDS storage for the IOPS anyway; might as well fill it up. Large object crew, who's with me?!
Lol. The most PG blob storage I've used in prod was a couple hundred GB. It was a hack and the performance wasn't ideal, but the alternatives were more complicated. Simple is good.
I like to Lob my BLOBs into PG's storage. You need that 1-2TB of RDS storage for the IOPS anyway; might as well fill it up. Large object crew, who's with me?!
that's not how this works. files are stored in s3, metadata in postgres
J/K. It could be a really good back-end option for Supabase's S3 front end. A lot of PG clients don't support proper "streaming" and looking at the codebase it's TypeScript.. postgres.js is the only client nearing "performant" I'm aware of(last I looked) on Node.js but it's not clear it supports streaming outside "Copy" per the docs. Support could be added to the client if missing.
Edit: Actually it could be a good option for your normal uploads too. Docs talk about it being ideal for 6Mb or smaller files? Are you using bytea or otherwise needing to buffer the full upload/download in memory? Streaming with Lob would resolve that, and you can compute incremental hash sums for etags and etc. Lob has downsides and limitations but for a very large number of people it has many great benefits that can carry them very far and potentially all the way.
Earlier quoted context omitted.
Our S3 Driver is compatible with any S3 Compatible object Storage so you don’t have to write one :)
I’m confused about what directions this goes. The announcement is that Supabase now supports (user) —s3 protocol—> (Supabase) Above you say that (Supabase) —Supabase S3 Driver—> (AWS S3) Are you further saying that that (Supabase) —Supabase S3 Driver—> (any S3 compatible storage provider) ? If so, how does the user configure that? It seems more likely that you mean that for any application with the architecture (user…
(user) -> s3 protocol -> (Supabase) -> (AWS S3)
you could fork (or contribute) a database driver for any s3 compatible backend of choice.
(user) -> s3 protocl -> (pbronez-base) -> (GCP Cloud Storage)