News for hackers. Stuff that matters.
Re:The Marketing Behind MongoDB by mohaine on Wednesday August 30, 2017 @01:55PM (#15134360)
I understand that they do persist to disk and store data differently but the ones I've seen used in practice are in memory during runtime. It as been a few years but so maybe this has changed. Any examples?

Graph databases also are only fast when doing graph transversal lookups. They all have index just like RDB. Sure you got from parent->child->grandchild quickly but how to do you find the parent in the first place? An index normally.

Re:The Marketing Behind MongoDB by EGreg on Wednesday August 30, 2017 @06:28PM (#15136648)
But the parent is one lookup and the children are 1000. Thats why.
Re:The Marketing Behind MongoDB by mohaine on Friday September 01, 2017 @10:40AM (#15148671)
This is only if the 1000 children are already in memory. Otherwise it is still 1000 lookups, by index. This is why the Graph Dbs on the market tend to be in memory.

I'm not saying Graph DBs don't have their place. They do, but they are the wrong answer for MOST datasets.

Re:The Marketing Behind MongoDB by EGreg on Sunday September 03, 2017 @12:25PM (#15162254)
NO. Each lookup thereafter is NOT by index. That's where the savings come from. The pointers already contain the exact block where to load the info from.