II.
StackPart overview
Reference · livestack-part:graph-database
Graph Database overview
Database purpose-built for storing and traversing graph structures — nodes (entities) and edges (relationships) with properties on both. Graph databases excel at multi-hop relationship queries that would require expensive recursive joins in a relational database. Common use cases: fraud detection, recommendation engines, knowledge graphs, identity and access management, and social networks. Neo4j uses the Cypher query language; Amazon Neptune supports Gremlin and SPARQL; Dgraph uses GraphQL+DQL. Property graphs (Neo4j, Neptune) and RDF triplestores (Stardog, Amazon Neptune/SPARQL) are the two dominant paradigms. Vector + graph hybrids are emerging for AI knowledge graph applications.
Attributes
displayName
Graph Database
category
data-store
description
Database purpose-built for storing and traversing graph structures —
nodes (entities) and edges (relationships) with properties on both.
Graph databases excel at multi-hop relationship queries that would
require expensive recursive joins in a relational database.
Common use cases: fraud detection, recommendation engines, knowledge
graphs, identity and access management, and social networks. Neo4j
uses the Cypher query language; Amazon Neptune supports Gremlin and
SPARQL; Dgraph uses GraphQL+DQL. Property graphs (Neo4j, Neptune) and
RDF triplestores (Stardog, Amazon Neptune/SPARQL) are the two dominant
paradigms. Vector + graph hybrids are emerging for AI knowledge graph
applications.
Outgoing edges
implemented_by1
- tool:neo4j·ToolNeo4j
Incoming edges
implements_stack_part1
- tool:neo4j·ToolNeo4j
integrates_with1
- tool-server:mcp-neo4j·ToolServerNeo4j MCP Server