A Survey of RDF Stores & SPARQL Engines for Querying Knowledge Graphs

Abstract

Recent years have seen the growing adoption of non-relational data models for representing diverse, incomplete data. Among these, the RDF graphbased data model has seen ever-broadening adoption, particularly on the Web. This adoption has prompted the standardization of the SPARQL query language for RDF, as well as the development of a variety of local and distributed engines for processing queries over RDF graphs. These engines implement a diverse range of specialized techniques for storage, indexing, and query processing. A number of benchmarks, based on both synthetic and real-world data, have also emerged to allow for contrasting the performance of different query engines, often at large scale. This survey paper draws together these developments, providing a comprehensive review of the techniques, engines and benchmarks for querying RDF knowledge graphs.

MillenniumDB: A Persistent, Open-Source, Graph Database

“…A variety of query languages for graphs have been proposed down through the years [4], including AQL [31] (used by ArangoDB), Cypher [13] (used by Neo4j [44]), Gremlin [28] (used by Amazon Neptune [32], JanusGraph [33], Neo4j [44], OrientDB [38]), G-Core [2], GSQL [40] (used by TigerGraph [40]) SPARQL [15] (used by various systems [1], including Allegrograph [30], Amazon Neptune [32], Blazegraph [41], GraphDB [7], Jena TDB [34], Stardog [39] and Virtuoso [11]), SQL-Match [38] (used by Ori-entDB [38]).…”

“…In the context of NoSQL systems, Neo4j [44], which uses the query language Cypher [13], is a leading graph database system in practice. 1 Other popular graph database systems include ArangoDB [31], JanusGraph [33], OrientDB [38], TigerGraph [40], etc., which support Gremlin [28] and other custom graph query languages. We also find graph database systems supporting the RDF data model and SPARQL query language [1], including Allegrograph [30], Amazon Neptune [32], Blazegraph [41], GraphDB [7], Jena TDB [34], Stardog [39], Virtuoso [11], and (many) more besides [1].…”