I love GraphQL and use it quite a bit, but the "graph" part of it is a bit of a misnomer given all the existing graph database and query technologies. It doesn't really offer anything in terms of interacting with RDF triples or making complex graph queries. It has no relational algebra semantics or ability to query relationships between arbitrary nodes, which is what folks using graph databases typically want.

(I didn't downvote you though, it's a common misconception.)

> It doesn't really offer anything in terms of interacting with RDF triples or making complex graph queries.

SPARQL is supported.

Yes, I was talking about GraphQL.

I believed that GraphQL is more of an protocol for interacting with an api, and not for graph databases, which is what Gremlin and SparQL are used for.

GraphQL is not a graph database query language. It's an alternative to REST.

The lack of support of OpenCypher is also a bit intriguing.

GraphQL can in fact be a graph query language -- my company has built and open-sourced a tool that makes that possible. Here's a blog post that describes how it works: https://blog.kensho.com/compiled-graphql-as-a-database-query...

If you want to try it out:

  pip install graphql-compiler

I second all the comments about GraphQL not being a graph query language. But we must agree that 90% of the quries we run on a graph database could be modelized with GraphQL. (retrieve nodes of a given type plus some of their properties). For the 10% other percent, Gremlin or SPARQL are then the way to go.