Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Supabase-JS v2

supabase.com

Post reply on HN
Print view View original

71–80 of 82 posts

Re: Supabase-JS v2

#71

Post by crooked-v »

kiwicopple wrote: post #45
msdrigg wrote: post #44

Earlier quoted context omitted.

I tried to make this work for me, but I finally gave up this week and wrote a traditional backend component for part of my backend because supabase doesn't support transactions and I am NOT going to write my whole backend in postgres functions.

supabase does support transactions through RPC calls - I think you already understood that based on your comment but want to make the distinction clear for other readers I can completely understand if you don't to write everything in pgpsql though. Did you also try the Deno Functions? We've been brainstorming ways to support transactions directly from the client libs in a way that won't lock up the database if there…

Well, the simple case is to start with transactions with only queries that aren't dependent on each other, which would cover a vast majority of cases by itself - client sends an array of queries as a single network call, gets either an array back of results or a failure state.

Re: Supabase-JS v2

#72

Post by yashap »

bicijay wrote: post #16

I love supabase and im using it on one of my projects. The only downside is the storage abstraction on top of S3, those Egress fees are huge. I would love to see a Backblaze b2 integration.

I haven’t used Supabase, but would it not be easy/standard to stick a CDN between the end user and S3, so that S3 is only hit on CDN cache misses, and thus S3 egress is minimal?

Re: Supabase-JS v2

#74

Post by zinclozenge »

beaker52 wrote: post #41
zinclozenge wrote: post #5

Earlier quoted context omitted.

I think the best part is that if you're willing to go all in on RLS for your authorization, you can do away with needing a backend for your typical crud operations and use their functions for things like webhooks, or the occasional endpoint for more complicated operations.

I can't quite get onboard with RLS directly from the client. It seems like a risky and finicky thing to design database access patterns around, but they might be a stroke of genius that I'm too blind to see right now.

If you're not comfortable then that's totally ok, especially because it's not as easy to test it automatically, but it's definitely allowed me to do away with a backend completely except for a webhook, so that's been nice.

Re: Supabase-JS v2

#75

Post by zinclozenge »

Escapado wrote: post #60
mildmustard wrote: post #26

Earlier quoted context omitted.

Absolutely. I find myself saying this a lot when I try and explain the concept of Supabase. We don't really emphasize this very much on our website either. Disclaimer: I work at Supabase.

I am a happy paying user of supabase and I did just that for my project which is meant to facilitate trading of left over wood between woodworker shops. I simply set RLS rules and now I only have a react frontend which calls supabase directly and it works great. I haven't checked in a while but one thing that was a little cumbersome for me was that I wasn't familiar with writing proper RLS rules and felt like documen…

I would say it's definitely one of the missing pieces in their documentation. They have an example policy for the typical scenario of only allowing a user to read/update/delete their own resources, but there's definitely more patterns that are needed. One that took me a bit to figure out on my own was how to only allow a user access to a resource gated behind a subscription (ie a column value in a table).

Re: Supabase-JS v2

#76

Post by kiwicopple »

evelynsalt wrote: post #70

What is the difference between Supabase and PostgREST https://postgrest.org/en/stable/ I know Supbase is a sponsor of the PostgREST.

Supabase uses PostgREST as an API server on top of you Postgres database: https://supabase.com/docs/architecture

We are a sponsor and we employ the maintainer of PostgREST

Re: Supabase-JS v2

#77

Post by cpursley »

bsimpson wrote: post #31

It's wild that their whole value proposition seems to be "It's a Firebase clone, but open source."

Their value proposition is that it's as easy as Firebase, but built on the rock solid Postgres.

Re: Supabase-JS v2

#78

Post by kiwicopple »

jlbprof wrote: post #73

I cannot find an "about" page. What is Supabase?

Supabase is an open source Firebase alternative. We're building the _features_ of Firebase using open source tools: Postgres Database, Authentication, auto-generated APIs (PostgREST), Realtime subscriptions, and File Storage.

more details here: https://supabase.com/docs/architecture

Re: Supabase-JS v2

#80

Post by Marlon1788 »

cool v2, I was looking at supabase for my startup on the weekend and dropped it because I had a hard time working out types. Happy to see type release and will check out V2.

I agree with Krono & jibprof about a brief description, please create an about or a better mission statement (other then "open source firebase") on the main page.

and congratz on funding kia ora!

Post reply on HN