Neo4j is a graph database that is natively designed to store and query graph data. It uses a graph-native architecture that optimizes for storing and traversing relationships between nodes. This allows Neo4j to provide faster performance on workloads involving connected data compared to traditional databases.
26. Connectedness and Size of Data Set
ResponseTime
Relational and
Other NoSQL
Databases
0 to 2 hops
0 to 3 degrees
Thousands of connections
1000x
Advantage
Tens to hundreds of hops
Thousands of degrees
Billions of connections
Neo4j
“Minutes to
milliseconds”
Real-Time Query Performance
31. Graph Native Approach
• Declarative query language
• Human readability
• Graph expressiveness
• Optimizer and Query Planner for graphs
• Graph metadata
• Runtime metadata
• Aim to work in main memory
• And optimize for L2 where possible
• Maximize IO performance
• Graph traversals by pointer chasing
51. Bookmark
• Session token
• String (for portability)
• Opaque to application
• Represents ultimate user’s most recent
view of the graph
• More capabilities to come