图数据库与关系数据库
理解 Neo4j 等图数据库与传统关系数据库之间的核心差异，以及各自适用的场景。
图数据库与关系数据库 是 CoddyKit 上的免费 Neo4j Graph Database Fundamentals 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Neo4j Graph Database Fundamentals 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Neo4j Graph Database Fundamentals 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Two Ways to Model Data
Two ways to model data: relational stores tables of rows and columns; graph stores nodes linked by relationships. They optimize for different access patterns.
The Relational Model
In a relational database, connections live as foreign keys and get resolved at query time with JOINs.
SELECT u.name, o.total
FROM users u
JOIN orders o ON o.user_id = u.id
WHERE u.id = 42;The Graph Model
In a graph, the relationship is a first-class object stored right between two nodes — no join table or foreign-key lookup needed.
MATCH (u:User {id: 42})-[:PLACED]->(o:Order)
RETURN u.name, o.total;The Cost of JOINs
Every relational JOIN scans and matches keys, so multi-hop queries (friends of friends of friends) get pricey fast. Graphs traverse stored links, staying quick.
Index-Free Adjacency
With index-free adjacency, each node points straight to its neighbors — walking a relationship is a pointer hop, so traversal stays fast at any scale.
Schema Flexibility
Relational schemas are rigid and need migrations. Graphs are schema-optional: add new labels, relationships, and properties without touching existing data.
Where Relational Wins
Relational wins for highly structured tabular data, heavy aggregation and reporting, and transactions over many uniform rows. If your data is a spreadsheet, use a table.
Where Graphs Win
Graphs win when relationships are the point: social networks, recommendation engines, fraud detection, and knowledge graphs.
A Concrete Comparison
Find friends-of-friends: relational needs a chain of self-joins, while a graph just expresses it as a path pattern. Compare the two.
MATCH (me:Person {name: 'Alice'})-[:FRIEND]->()-[:FRIEND]->(fof)
WHERE fof <> me
RETURN DISTINCT fof.name;Hybrid Architectures
You don't have to pick one. Many systems pair a relational store for transactions with a graph for relationship-heavy queries, syncing between them.
Choosing the Right Tool
Ask yourself: are my most important questions about connections? If yes, a graph likely simplifies both your model and your queries.
Quick Check
Check your understanding of the two models.
Recap
You compared the models: relational uses tables and JOINs, graphs store relationships directly with index-free adjacency, and hybrid setups are common.
常见问题解答
「图数据库与关系数据库」课时是免费的吗？
是的 — 「图数据库与关系数据库」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Neo4j Graph Database Fundamentals 课程的其余内容，请升级到 CoddyKit PRO。 Neo4j Graph Database Fundamentals 课程共包含 4 节课。
「图数据库与关系数据库」这节课中我会学到什么？
理解 Neo4j 等图数据库与传统关系数据库之间的核心差异，以及各自适用的场景。 你通过在浏览器中直接运行的动手代码来练习 Neo4j Graph Database Fundamentals，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Neo4j Graph Database Fundamentals 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Neo4j Graph Database Fundamentals 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「图数据库与关系数据库」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Neo4j Graph Database Fundamentals 课中编写并运行代码吗？
能。每节 Neo4j Graph Database Fundamentals 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 什么是图数据库
- Neo4j 及其架构简介
- 设置 Neo4j 环境
- 图数据库与关系数据库