- Overview
- Alternatives
- Pros & Cons
- Compare
- PostGraphile automatically generates a GraphQL API from your PostgreSQL database schema
- Database-Driven Development
- Makes use of PostgreSQL's row-level security
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.
Database-Driven Development
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?
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.
Information found on this page is crowd-sourced by the community and contains the most agreed upon PostGraphile Pros and Cons. Which allows you to determine advantages and disadvantages of using PostGraphile and pinpoint PostGraphile's strengths and weaknesses. Anyone that have used PostGraphile can post their own views of the software, vote on the accuracy of other users claims, and help more people is the process of doing so.
This page was last updated on Wed 21 Jun 2023 (9 months, 3 weeks ago).