Hacker News Reader

Was it, or was it the year of graphql? The latter making the former more approachable.

GraphQL has nothing inherently to do with graph databases. It's a client-side declarative syntax where you specify what result you want, usually including composite relational objects.

The server-side database would be any supported datastore.

I don't disagree at all, but query languages like "SPARQL" and "Cypher" are no where nearly as approachable as the query by example like syntax of "GraphQL" (resolvers aside).

My feeling is that GraphQL has opened up a pathway and other than that I personally did not observe any other kind of sea change in the graph database landscape.

How do you implement and/or in graphql A quick search shows you have to implement the whole thing yourself

Sparql is not unapproachable at all, after one has learned the basics. It's not more difficult than traditional sql queries.

Reply on news.ycombinator.com