NEW
Also known as: Graph DB, Property Graph Database
Database that stores data as nodes and edges, optimized for traversing and querying relationships.
DESCRIPTION
Graph databases represent entities as nodes and relationships as edges with properties, enabling efficient traversal of connected data. They support use cases like social networks, fraud detection, recommendations, and knowledge graphs. Query languages include Cypher, Gremlin, and SPARQL for property graphs and RDF stores. Index-free adjacency and specialized storage accelerate relationship-centric queries. They complement relational systems by modeling complex networks naturally.
ALTERNATIVE DEFINITIONS
AWS
A graph database is a type of database that uses graph structures for semantic queries, with nodes, edges, and properties to represent and store data.
Defines core structures and semantic query focus.
Neo4j
A graph database uses graph structures with nodes and relationships to represent and store data.
Highlights property graph model with relationships as first-class citizens.
RELATED TERMS
Knowledge Graph Triple Store RDF Store Neo4j Apache TinkerPop Gremlin Cypher SPARQL Network Analysis Graph Query
COMPETING TERMS
Relational Database Document Database Key-Value Store
RELATIONS
- Broader: Database
- Narrower: Amazon Neptune
KNOWLEDGE AREAS
Data Storage & Operations Data Architecture Semantic & Knowledge Modeling Data Engineering
TARGET AUDIENCE
Data Architect Data Engineer AI Engineer Data Scientist
EXTERNAL SOURCES
- Wikipedia - Graph database
- Neo4j - Comprehensive graph database documentation
- Apache TinkerPop - Graph computing framework and Gremlin
- Amazon Neptune - Managed graph database overview
- W3C - RDF primer for graph data
TOP QUESTIONS
When should a Graph Database be used?
Use it when relationships are central, frequent traversals are needed, and data is highly connected, such as social networks, fraud detection, and recommendations.
Category: Requirements
How does a Graph Database differ from a Relational Database?
Graph databases model relationships explicitly and traverse efficiently; relational databases rely on joins over tabular schemas.
Category: Distinction
What query languages do Graph Databases support?
Property graphs use Cypher and Gremlin; RDF stores use SPARQL.
Category: Overview
What is index-free adjacency in Graph Databases?
It stores direct pointers between nodes, enabling fast traversals without indexing overhead.
Category: Concept
What are common mistakes with Graph Databases?
Over-modeling attributes as nodes, ignoring schema evolution, and not planning for traversal patterns can harm performance and maintainability.
Category: Mistakes
Are Graph Databases scalable for large datasets?
Yes, many support clustering and sharding; design for traversal locality and balanced partitions is crucial.
Category: Risk
Can Graph Databases integrate with BI tools?
Integration is possible via connectors, exporting tabular views, or specialized graph analytics interfaces.
Category: Collaboration
How do Graph Databases support knowledge graphs?
They store entities and relationships with semantics, enabling reasoning, link prediction, and exploration.
Category: Example
Which engines provide Graph Database capabilities?
Neo4j, Amazon Neptune, JanusGraph, and ArangoDB are common options.
Category: Overview