4 ms·

I never quite understood Apollo. I've written GraphQL servers using just the Node.js GraphQL implementation and they haven't been much code. Barely more boilerp

by throwaway2016a 9y ago

I never quite understood Apollo. I've written GraphQL servers using just the Node.js GraphQL implementation and they haven't been much code. Barely more boilerplate than the Apollo example given. I'll have to dive into the code myself when I have some free time but can anyone explain to me what value this adds specifically? I am assuming it does add value and I'm just not seeing it.

djmashko2 9y ago
Hey, I'm on the Apollo team! As mentioned in the blog post, this is just a thin wrapper around the regular GraphQL.js implementation, with a few small bells and whistles added! The intention of this library isn't to change a lot about how GraphQL servers are written, it's just a stable, community focused library to bind your GraphQL server to a schema.
- throwaway2016a 9y ago
  Hi djmashko2, thank you for your reply and keep up the good work. I'm not sure that answers my question though. I'd like to know which things it makes easier. Maybe a side by side with the "traditional way" vs "the Appolo way" Looking at the website, it looks like it makes the benefit of Apollo client relatively clear, I'm still not sure about the server piece.
  - djmashko2 9y ago
    This is a great answer: https://news.ycombinator.com/item?id=14816423 https://news.ycombinator.com/item?id=14816423
batmansmk 9y ago
From the doc: Comparison with express-graphql - express-graphql works with Express and Connect, Apollo Server supports Express, Connect, Hapi, Koa and Restify. - Compared to express-graphql, Apollo Server has a simpler interface and supports exactly one way of passing queries. - Apollo Server separates serving GraphiQL (an in-browser IDE for exploring GraphQL) from responding to GraphQL requests. - express-graphql contains code for parsing HTTP request bodies, Apollo Server leaves that to standard packages like body-parser. - Apollo Server includes an OperationStore to easily manage whitelisting. - Apollo Server is built with TypeScript.
- throwaway2016a 9y ago
  Thank you for digging that up. You don't need to use express-graphql to use graphql on a server so that comparison is only meaningful if you already use a wrapper... I'm was curious why a wrapper is even needed. The base GraphQL.js library is not complicated. The Apollo team member himself even said the wrapper is "thin."

djmashko2 9y ago

Hey, I'm on the Apollo team! As mentioned in the blog post, this is just a thin wrapper around the regular GraphQL.js implementation, with a few small bells and whistles added! The intention of this library isn't to change a lot about how GraphQL servers are written, it's just a stable, community focused library to bind your GraphQL server to a schema.

throwaway2016a 9y ago
Hi djmashko2, thank you for your reply and keep up the good work. I'm not sure that answers my question though. I'd like to know which things it makes easier. Maybe a side by side with the "traditional way" vs "the Appolo way" Looking at the website, it looks like it makes the benefit of Apollo client relatively clear, I'm still not sure about the server piece.
- djmashko2 9y ago
  This is a great answer: https://news.ycombinator.com/item?id=14816423 https://news.ycombinator.com/item?id=14816423

batmansmk 9y ago

From the doc: Comparison with express-graphql - express-graphql works with Express and Connect, Apollo Server supports Express, Connect, Hapi, Koa and Restify. - Compared to express-graphql, Apollo Server has a simpler interface and supports exactly one way of passing queries. - Apollo Server separates serving GraphiQL (an in-browser IDE for exploring GraphQL) from responding to GraphQL requests. - express-graphql contains code for parsing HTTP request bodies, Apollo Server leaves that to standard packages like body-parser. - Apollo Server includes an OperationStore to easily manage whitelisting. - Apollo Server is built with TypeScript.

throwaway2016a 9y ago
Thank you for digging that up. You don't need to use express-graphql to use graphql on a server so that comparison is only meaningful if you already use a wrapper... I'm was curious why a wrapper is even needed. The base GraphQL.js library is not complicated. The Apollo team member himself even said the wrapper is "thin."