Home / Companies / Neo4j / Blog / Post Details
Content Deep Dive

Will It Graph? Identifying a Good Fit for Graph Databases  –  Part 1

Blog post from Neo4j

Post Details
Company
Date Published
Author
Lju Lazarevic
Word Count
1,484
Language
English
Hacker News Points
-
Summary

A native graph database is a type of database that stores data in nodes and relationships between those nodes, unlike relational databases which store data in tables with rows and columns. In a graph database, each node represents a discrete entity, such as a person or an address, and the relationships between nodes represent connections between entities. This allows for more efficient querying and pattern matching compared to traditional relational databases, where joins are used to connect related data. Graph databases offer several advantages, including faster query performance, especially for JOIN-heavy applications, and improved ability to query complex patterns. However, they also come with trade-offs, such as slower write performance due to the need to materialize relationships at write time. The choice between a graph database and a relational database depends on the specific needs of the application and the desired balance between read and write performance.