Need advice about which tool to choose?Ask the StackShare community!
Apollo vs GraphQL: What are the differences?
Apollo: GraphQL server for Express, Connect, Hapi, Koa and more. Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes; 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.
Apollo belongs to "Platform as a Service" category of the tech stack, while GraphQL can be primarily classified under "Query Languages".
"From the creators of Meteor" is the top reason why over 8 developers like Apollo, while over 61 developers mention "Schemas defined by the requests made by the user" as the leading cause for choosing GraphQL.
Apollo and GraphQL are both open source tools. It seems that GraphQL with 11.7K GitHub stars and 753 forks on GitHub has more adoption than Apollo with 7.55K GitHub stars and 940 GitHub forks.
Facebook, Instagram, and Twitter are some of the popular companies that use GraphQL, whereas Apollo is used by CircleCI, Swat.io, and Flexport. GraphQL has a broader approval, being mentioned in 561 company stacks & 750 developers stacks; compared to Apollo, which is listed in 131 company stacks and 127 developer stacks.
Pros of Apollo
- From the creators of Meteor12
- Great documentation7
- Open source3
- Real time if use subscription2
Pros of GraphQL
- Schemas defined by the requests made by the user75
- Will replace RESTful interfaces63
- The future of API's62
- The future of databases49
- Self-documenting13
- Get many resources in a single request12
- Query Language6
- Ask for what you need, get exactly that6
- Fetch different resources in one request3
- Type system3
- Evolve your API without versions3
- Ease of client creation2
- GraphiQL2
- Easy setup2
- "Open" document1
- Fast prototyping1
- Supports subscription1
- Standard1
- Good for apps that query at build time. (SSR/Gatsby)1
- 1. Describe your data1
- Better versioning1
- Backed by Facebook1
- Easy to learn1
Sign up to add or upvote prosMake informed product decisions
Cons of Apollo
- File upload is not supported1
- Increase in complexity of implementing (subscription)1
Cons of GraphQL
- Hard to migrate from GraphQL to another technology4
- More code to type.4
- Takes longer to build compared to schemaless.2
- No support for caching1
- All the pros sound like NFT pitches1
- No support for streaming1
- Works just like any other API at runtime1
- N+1 fetch problem1
- No built in security1
Sign up to add or upvote consMake informed product decisions
What is Apollo?
What is GraphQL?
Need advice about which tool to choose?Ask the StackShare community!
What companies use GraphQL?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Apollo?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+7
+32
+17
+47