Need advice about which tool to choose?Ask the StackShare community!
GraphQL vs PostGraphile: What are the differences?
GraphQL: A data query language and runtime. GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012; PostGraphile: Instant GraphQL API for your PostgreSQL database; use standalone or as a Node.js middleware; MIT-licensed OSS. Execute one command (or mount one Node.js middleware) and get an instant high-performance GraphQL API for your PostgreSQL database.
GraphQL and PostGraphile belong to "Query Languages" category of the tech stack.
Some of the features offered by GraphQL are:
- Hierarchical
- Product-centric
- Client-specified queries
On the other hand, PostGraphile provides the following key features:
- instant GraphQL schema via reflection over PostgreSQL database API
- compiles complex GraphQL queries into very few SQL statements resulting in high performance
- built entirely from plugins - heavily customisable
GraphQL and PostGraphile are both open source tools. GraphQL with 11.7K GitHub stars and 753 forks on GitHub appears to be more popular than PostGraphile with 7.49K GitHub stars and 364 GitHub forks.
Pros of GraphQL
- Schemas defined by the requests made by the user74
- Will replace RESTful interfaces62
- The future of API's60
- The future of databases48
- Self-documenting12
- Get many resources in a single request11
- Query Language5
- Ask for what you need, get exactly that5
- Fetch different resources in one request3
- Evolve your API without versions3
- Type system3
- Easy setup2
- GraphiQL2
- Ease of client creation2
- Good for apps that query at build time. (SSR/Gatsby)1
- Backed by Facebook1
- Easy to learn1
- "Open" document1
- Better versioning1
- Standard1
- 1. Describe your data1
- Fast prototyping1
Pros of PostGraphile
- Postgres based authentication10
- Great developer support6
- Lightning fast5
- Database first with no braking changes5
- Simple to set up and scale4
- Bye bye Resolvers4
- Back to database first3
- 9 Automatically generates your GraphQL schema3
- Easy setup of relationships and permissions3
- Instant production ready GraphQL3
- Works with new and existing databases1
Sign up to add or upvote prosMake informed product decisions
Cons of GraphQL
- Hard to migrate from GraphQL to another technology4
- More code to type.4
- Takes longer to build compared to schemaless.2
- All the pros sound like NFT pitches1
- Works just like any other API at runtime1