Sparkier, faster, more: Graph databases, and Neo4j, are moving on
New players, new features, platforms, and ticking boxes. Let’s talk graph with Neo4j.
A lot has happened in graph land in the last six months. Quick recap: a new player (TigerGraph), Microsoft ramping up its graph play with graph support in SQL Server and CosmosDB, and the number two graph database, OrientDB, getting acquired.
The number one graph database, Neo4j, is kicking off its Graph Connect event today and announcing a new version, 3.3. This version brings extended support for querying in Spark, ETL, analytics, and improved performance. We discuss the developments and what they mean for this space with Neo4j’s CEO, Emil Eifrem.
One of the pain points in the graph space at the moment is querying. Not that you can’t query graphs, but there may actually be too much of a choice there. It’s almost as if every platform has its own query language.
Since there is no such thing as a SQL for graphs yet, this leaves an empty space that invites competition for the one graph query language that will become dominant. Some of the most widely languages/APIs used for graph querying are SPARQL, Gremlin, and Cypher.