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.
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.
The Apollo team member himself even said the wrapper is "thin."
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.
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.