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.
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."
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.
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.
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.