Native Property Graph Databases
14 entriesPurpose-built graph engines storing nodes, edges and properties.
Multi-Model Databases with Graph
5 entriesDatabases that combine graph with document, key-value, search or relational models.
RDF, SPARQL & Semantic Graph Stores
8 entriesTriple stores and semantic platforms for knowledge graphs.
Cloud & Relational-integrated Graph
6 entriesManaged graph services and graph features inside existing databases.
Standards, Benchmarks & Rankings
11 entriesQuery-language standards and independent resources for comparing graph databases.
Related Pages
1 entriesNeighbouring pages on this site.
Frequently Asked Questions
What is a graph database?
A graph database stores data as nodes and edges with properties, so relationship traversal is fast compared with relational joins, which suits fraud detection, recommendations, knowledge graphs and network analysis.
Property graph or RDF?
Property graphs (Neo4j, TigerGraph, Memgraph) are queried with Cypher, GQL or Gremlin and suit applications, while RDF stores (GraphDB, Stardog, AllegroGraph) use SPARQL and suit linked data and knowledge graphs.
What is the GQL standard?
GQL is the ISO standard query language for property graphs, published in 2024 and closely related to openCypher. Support is growing across vendors.
Which graph database should I start with?
Neo4j and Memgraph have the largest communities, Amazon Neptune and Spanner Graph suit cloud-native teams, and Apache AGE adds graph queries to PostgreSQL.
Why was Apache Giraph removed?
Apache Giraph has been retired to the Apache Attic, so it is no longer an active project.