CODEWITHSUNDEEP
graphrdbmsgraph-databases
sreeraag
sreeraag

Reputation: 523

Why is an RDBMS bad to store a considerably big graph?

I started using a graph database to store a big graph that im generating. But im not convinced as to why to use a graph database to do my job, and why not do what i want with a conventional RDBMS. My question in specific is, why is a Relational Database bad or rather Graph Database is BETTER than RDBMS to store graphs?

Upvotes: 3

Views: 401

Answers (1)

rayseaward
rayseaward

Reputation: 328

After reading Graph Databases (early release, available here: http://graphdatabases.com/) it all comes down to performance. Depending on how deep or recursive your query is, the longer it will take for your RDBMS or graph database to return results. Traditional RDBMS are not designed for the quick traversal of relationships between entities whereas graph databases are built specifically for this. This may not be an issue if your recursion is only 2 levels deep but after this level performance apparently degrades significantly.

Please take this with a grain of salt. This is coming directly from Graph Databases and I have not replicated these results.

Upvotes: 2

Related Questions