3 ms·
AIUI, graph databases have much less impedance mismatch to objects than SQL databases do. So why are most people still using SQL? Tradition, or efficiency?
by cabalamat 16y ago
AIUI, graph databases have much less impedance mismatch to objects than SQL databases do. So why are most people still using SQL? Tradition, or efficiency?
- lucifer 16y agoNot everything is an object. Also you should try coding against both object and graph dbs from an (OO) domain model. Object identity is a fundamental problem that has nothing to do with the fact that a RDBMS is your persistent back-end. Also, consider the notion of 'dirty' objects as just one of the problems. Finally, you still have to manage (to some extent; per your db ymmv) relationship semantics. Object and graph dbs shine where you wish to traverse your object graph. That is what is painful (and entirely alien) to RDBMS notions. So if your application domain is naturally mapped to traversal semantics, then it is simpler (but note that you certainly can write complex joins that would support the same) and more importantly, the db engine is tuned to be highly efficient for such use cases.