3 ms·
Elegant to store, hell to really query. Continuing with your example of comments, it makes every query you have to do into a map reduce job, and simple fast thi
by 3pt14159 12y ago
Elegant to store, hell to really query. Continuing with your example of comments, it makes every query you have to do into a map reduce job, and simple fast things that used to be easy end up being a pain.
Certainly useful when you really need a graph, but I don't find that it is a cure-all.
- hugofirth 12y agoI would generally agree that you should only go the graph dbms route when you actually need to. However I would attach the caveat that a lot more people need to than you might think. Almost any domain where you want to do some kind of 'deep' traversal or non trivial pattern matching is going to benefit hugely from a native graph data model.
- glesica 12y agoNot necessarily. If you have an index into the posts and you want all the comments for a given article you can find the post quickly and the comments are just one hop away from that. Beyond that it's just like SQL (order by, limit, etc.).