I wrote about GraphQL on here before [1]. I don't share the author's enthusiasm that it's "awesome" that "the schema is all backed by arbitrary code" -- I think this is a bad trade-off, because you still have to have some custom data-munging layer between your GraphQL acceptor and your backend datasources, just like you had to do to, but with different code, to implement a REST service.<p>However, once canned ORMs or datastores that natively understand GraphQL (like dgraph) become available, the ecosystem will definitely enable rapid integration -- provided we keep in mind the lessons learned about user-supplied queries from the early SQL-on-the-web days.<p>[1] <a href="https://hn.algolia.com/?query=niftich%20graphql&sort=byDate&type=comment" rel="nofollow">https://hn.algolia.com/?query=niftich%20graphql&sort=byDate&...</a>