All these GraphQL solutions seem to focus on the frontend and assume there's a magical GraphQL server somewhere. But GraphQL Just shifts the hard work from the client to the server and I haven't seen any good solution towards security (except storing all the possible queries a user may access, which kind of defeats the purpose of GraphQL in the first place) and performance (a large query is usually resolved to thousands of database fetches, instead of 1 optimized one) on the server side.<p>What we really need is a decent GraphQL server. The client isn't difficult anyway.
Hey :-) we just announced this. Happy to answer any questions. Here's the accompanying blog post <a href="https://dev-blog.apollodata.com/learn-apollo-build-graphql-apps-with-react-react-native-or-exponent-4787269a4747" rel="nofollow">https://dev-blog.apollodata.com/learn-apollo-build-graphql-a...</a>
I came to the comments to point out that I didn't know what Apollo was. Most of your long term traffic will come from Google searches but early on while it's being shared around places like Hacker News, it's probably a good idea to add a link to <a href="http://dev.apollodata.com/" rel="nofollow">http://dev.apollodata.com/</a> to the intro.
Because they don't tell you on the site:<p>Apollo Client is a Javascript library that can be used in any front end where you want to use data from a GraphQL server.<p>It's incrementally adoptable, so that you can drop it into an existing JavaScript app and start using GraphQL for just part of your UI.<p>It uses TypeScript.