starter VS graphile-engine

I've been enjoying developing on top of PostGraphile. https://www.graphile.org/

Good starter: https://github.com/graphile/starter

I can add a column the the db, and my frontend gets that autimagically (in dev mode, it generates a graphql schema out of the db, and from that it creates composables for my frontend wiht graphql-codegen). On the frontend I use Vue 3, the starter is build with nextjs/react.

I learned so much about postgresql and RLS from postgraphile starter project: https://github.com/graphile/starter/blob/main/%40app/db/migr...

also the project is worth checking out ;)

I'm a fairly seasoned developer, but I've started contributing to a project (graphile-starter) where the core business logic is defined in PL/pgSQL functions and realized I have a lot to learn.

Someone called it: "hasura for adults”

It's highly customisable, works directly with postgresql row levels security and the performance is quite good. It has a custom GraphiQL gui to work on queries/mutations.

To really see how it all works together checkout the starter project: https://github.com/graphile/starter it has migrations, job queue, graphql-codegen etc.

Benjie (https://github.com/benjie) is one of the greatest maintainers I've ever seen!

Here’s a full stack, batteries included example: https://github.com/graphile/starter it doesn’t have mobile app yet but could be added relatively easily.

Postgraphile starter uses most of the same tech and has all the same functionality as far as I can tell, with the additional benefit of Postgraphile generating your GraphQL schema and resolvers instead of worrying them manually.

Check out the Postgraphile Starter and how it handles auth and sessions in a graphql api

But it doesn’t have to work this way. Some modern databases support a feature called "row-level security". It allows you to define access control policies at the row level based on the current user’s attributes (id, role, group membership, etc.). As long as the application can securely pass the current user’s identity to the database, it can leave all authorization checking to the database. And since the rules are defined at the table level instead of the API level, it has a much smaller surface to protect. The "row-level security" feature is the foundation of products like PostgREST, PostGraphile, and Supabase.

I really love the way pg-sql2 is going about that.

I've been enjoying developing on top of PostGraphile. https://www.graphile.org/

Good starter: https://github.com/graphile/starter

I can add a column the the db, and my frontend gets that autimagically (in dev mode, it generates a graphql schema out of the db, and from that it creates composables for my frontend wiht graphql-codegen). On the frontend I use Vue 3, the starter is build with nextjs/react.

I don't much direct knowledge on the internals, but here's a snippet from the graphile-engine repo README: