JasonL9000

4 ms·

1. 1.▲
   by JasonL9000 12y ago

   Even Arthur Cayley might have smirked at that one. :)
2. 2.▲
   by JasonL9000 12y ago

   Getting performance out of a graph often depends on being able to express your query effectively. The last thing you want to do is plunk down a cursor on a node and have your client start wandering around the graph, following edges. All tha
3. 3.▲
   by JasonL9000 12y ago

   Maybe so. Orly has a somewhat leveldb-like component called a Repo which might slot in well. A Repo is a log-structured merge storage system that also provides indexing, access to previous values, and, most importantly, consistent reads and
4. 4.▲
   by JasonL9000 12y ago

   A graph can do what a table can do and a lot more, but that's usually not the whole issue. In practice you need to consider things like speed, volume, scale, consistency, redundancy, computation, ad-hoc vs. planned operations, use of r
5. 5.▲
   by JasonL9000 12y ago

   I have. I'm on the team that's been developing it for the past four years. It's nice to see graph databases getting some popular traction at last. (I was into them before they were cool, of course.) I've only just starte