PostGraphile (previously known as PostGraphQL) is a free an open-source software project that lets you spin up GraphQL APIs on top of an existing PostgreSQL database, instantly. PostGraphile automatically detects tables, columns, indexes, relationships, views, types, functions and comments in your database. Based on that information it generates a GraphQL server and API which is automatically updated when changes are made to the database or its data.
Pros & Cons of PostGraphile
Makes use of PostgreSQL's row-level security
PostGraphile is built around features native to PostgreSQL. One such feature is PostgreSQL's row-level security, which can be utilized to build application authentication, authorization and role-based access systems right into your database.
Everything in PostGraphile revolves around your database schema. You write SQL, and PostGraphile automatically generates your GraphQL API. At first I was sceptical towards the model of database-driven development, but it has taught me how powerful our relational databases really are. As of late, the trend has been to move further and further away from database layer, with the introduction of ORMs, NoSQL, Serverless etc.. maybe these ideas are misguided?
PostGraphile automatically generates a GraphQL API from your PostgreSQL database schema
I love the fact that PostGraphile automatically detects tables, columns, indexes, relationships, views, types, functions and comments from my PostgreSQL database schema and instantly creates a GraphQL server and GraphiQL interface. With PostGraphile I can focus on what's important, making my idea come to reality, instead of fiddling with tooling.
Add a Pro or Con
Only members can post Pros & Cons
Creating your profile only takes a matter of seconds, or login with an existing account.