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

GraphQL is now available on Supabase

supabase.com

Post reply on HN
Print view View original

21–30 of 49 posts

Re: GraphQL is now available on Supabase

#21

Post by kiwicopple »

tomatowurst wrote: post #19

been curious as to what sort of savings you've been able to get with supabase because we are approaching a few thousand dollars to store a couple terabytes on DynamoDB Thinking of buying a dedicated server from Hetzner to run Supabase on it instead but worried about latency. awful that we have to move away from AWS for this but with four/five dedicated servers in EU, US-West, US-East, Singapore and Tokyo, we could ha…

One thing to mention is that DynamoDb and Postgres are vastly different databases, so the migration won't be a simple "dump and restore".

You're right - it will be a daunting task, but one that only becomes more daunting the longer you wait. If you make the migration to Hertzner + self-hosting (even just to pure Postgres), I'm certain you will see huge savings. It's hard to give exact numbers without knowing your workload, but feel free to reach out if you want to step through the numbers. We're not one-eyed about Supabase, but we feel that Postgres is a solid choice for your core-OLTP workloads. We love seeing more businesses adopt it. It's good for the ecosystem, and good for open source in general

Re: GraphQL is now available on Supabase

#22

Post by Dowwie »

kiwicopple wrote: post #2

hey HN, supabase ceo here. I'm really excited about this release. Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL…

How would you contrast this library with what EdgeDB is doing on top of Postgres?

Re: GraphQL is now available on Supabase

#23

Post by oliverrice »

Dowwie wrote: post #22
kiwicopple wrote: post #2

hey HN, supabase ceo here. I'm really excited about this release. Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL…

How would you contrast this library with what EdgeDB is doing on top of Postgres?

pg_graphql and EdgeDB both provide a graph-like query language on top of Postgres. EdgeDB

philosophically (I think) EdgeDB tries to do a more complete job of abstracting over Postgres. It has a custom query language (and GraphQL support via a plugin), and a migration system. Its runs separately from the DB.

In contrast, pg_graphql is more narrowly scoped. It enables you to query your existing Postgres database without caring how your data is structured or having any interactions with migrations. It also runs directly inside the database, so theres no separate process/server to manage.

The EdgeDB folks have a great comparison of GraphQL vs EdgeDB syntax on their site https://www.edgedb.com/docs/graphql/mutations

Re: GraphQL is now available on Supabase

#24

Post by 1st1 »

Dowwie wrote: post #22
kiwicopple wrote: post #2

hey HN, supabase ceo here. I'm really excited about this release. Our GraphQL implementation is built on top of pg_graphql[0], a PostgreSQL extension we open-sourced a few months ago. The implementation works with a lot of native PG functionality (like Row Level Security). You can also do a some neat things with PG GRANTS, enabling/disabling access to different tables/columns to effectively serve a different GraphQL…

How would you contrast this library with what EdgeDB is doing on top of Postgres?

EdgeDB [1] has indeed a rich GraphQL layer, but it's a very different project.

While it also builds on top of Postgres, EdgeDB replaces the entire relational database front-end. EdgeDB features a SQL replacement language called EdgeQL (analytical capabilities of SQL married with deep-fetching in GraphQL), a higher-level data model (tables -> object types), integrated migrations engine, a custom protocol with great performance & great client APIs, and many other things. Read more here [2].

(disclaimer: I'm EdgeDB co-founder)

[1] https://github.com/edgedb/edgedb

[2] https://www.edgedb.com/blog/edgedb-1-0

Re: GraphQL is now available on Supabase

#25

Post by zinclozenge »

syrusakbary wrote: post #18

Nice! I was already pretty excited about you guys, and this only fuels up more excitement since I always been a GraphQL lover. I'm impressed by the pace that you are releasing new products... keep it up team!

The Friday announcement is looking like they will announce functions/lambdas.

Re: GraphQL is now available on Supabase

#26

Post by alexkreidler »

Hi all, this sounds very cool. How does pg_graphql compare to Postgraphile? https://github.com/graphile/postgraphile (besides I guess running in the DB with PLpgSQL instead of as a NodeJS server)

Did you think about integrating Postgraphile with the Supabase ecosystem or have specific limitations with it?

Thanks!

Re: GraphQL is now available on Supabase

#28

Post by DenseComet »

tomatowurst wrote: post #19

been curious as to what sort of savings you've been able to get with supabase because we are approaching a few thousand dollars to store a couple terabytes on DynamoDB Thinking of buying a dedicated server from Hetzner to run Supabase on it instead but worried about latency. awful that we have to move away from AWS for this but with four/five dedicated servers in EU, US-West, US-East, Singapore and Tokyo, we could ha…

Take a look at ScyllaDB Alternator [1], which is API compatible with DynamoDB. Scylla also supports multiregion clusters, which should help with latency. I've not used alternator, but I've had a good experience with Scylla, and it might be worth looking into as a lower effort way to move off DynamoDB.

[1] https://www.scylladb.com/alternator/

Re: GraphQL is now available on Supabase

#29

Post by city41 »

andrew_ wrote: post #11
oliverrice wrote: post #8

Earlier quoted context omitted.

If you're an existing supabase customer you don't need to change any of your existing permissions. pg_graphql filters out any tables/columns that aren't accessible to the user making the request. It also respects your row level security policies. If you can't see something in the introspection schema, you'll get a friendly error if you try to access it. pg_graphql does not used any privileged access so the queries ar…

that's great, but what if I want to add a role to my user to do something like send an email with an extended schema (when that lands). What if I'm not familiar with "row level permissions" and I have a SaSS app where different users can access different rows based on column content? Scenarios like those are where the docs fall short. PLEASE think like new users and not like seasoned engineers with prior experience w…

Supabase's row level security is just postgres row level security, it's not proprietary to Supabase. Postgres documentation, blog posts etc on RLS will apply to Supabase too.
Post reply on HN