Graph Database
AI Engineer path · lesson 69 of 124Click through the property-graph model, run Cypher-style traversals compared to the equivalent SQL joins, and see illustrated use cases — the engine behind recommendations and knowledge graphs.
Key insight
In a property graph, nodes and edges aren't just connectors — each carries a label (:User, :Product) and its own key–value properties, just like a row would in a table. The difference is the relationship itself is a first-class, queryable thing with properties too (like PURCHASED {amount, date}), not a foreign key you have to join to reconstruct.
Node, relationship, or property?
Sort each piece of a property graph.
Tap a piece, then tap where it goes — or drag it. Tap the tray to take one back.
Node
Drop items hereRelationship
Drop items hereProperty
Drop items hereTest your knowledge
In a graph database, what does an edge represent?
The short version
A graph DB is a city map where roads (relationships) are first-class: "friends-of-friends who bought X" is following a couple of streets. The relational version is reconstructing those streets from a stack of address spreadsheets each time.
Interview Questions
References & Further Reading
Love this visualization?
Sign up to track your progress, earn achievements, use the AI assistant, and access your personal learning dashboard.
100% free • No credit card required