4 ms·

Curious how it compares to https://www.graphile.org/postgraphile/ https://www.graphile.org/postgraphile/

• samwillis 5y ago
  The article suggests they built it so that by running it within the DB it would have less compute overhead and they could match GraphQL requests to SQL transactions 1:1.
  • gregplaysguitar 5y ago
    Just noting that Graphile also uses transactions - that’s a given for this sort of tool I’d say.
• oliverrice 5y ago
  its very similar in goals to postgraphile as samwillis mentioned, the memory footprint is tiny, which is a big perk for supabase's platform (or if you're self hosting) but its also fully language agnostic which opens up lots of options for extensibility: For simple use-cases you can expose the graphql functionality over http using a PostgREST as described here https://supabase.github.io/pg_graphql/quickstart/ https://supabase.github.io/pg_graphql/quickstart/ but, if you want more configuration like adding in middleware or wiring it up to an existing backend application, you can do that from any programming language that can connect to postgres, rather than only javascript
• underbluewaters 5y ago
  I had to make sure someone had plugged postgraphile here. It's a great system. What impresses me most about it is how it grows with the complexity of your application. There are so many thoughtful points of extensibility built in, I always have confidence that I can go into the docs and find a way to do what I need to. That reminds me, I need to figure out how to get my employer to sponsor the project...
  • gardnr 5y ago
    You could hire one of the maintainers to consult on your project.