neunhoef

7 ms·

31.
by neunhoef 12y ago
Interesting article, did you consider any of the newer NoSQL solutions that offer a data model more similar to MongoDB but more, often configurable, consistency guarantees (like ArangoDB or RethinkDB)? I could imagine that the effort of a m
32.
by neunhoef 12y ago
Another good rule I tend to use is that if your queries will involve variable lengths of paths in your graph, it was probably a good idea to model using a graph. This is because another model would almost certainly need multiple joins, whic
33.
by neunhoef 12y ago
Right, you were quicker but are essentially saying the same thing as I said in my example.
34.
by neunhoef 12y ago
Say you have one collection for your people (sharded over 100 servers, say) and another one for conferences (also sharded over 100 machines). Then you could hold the primary keys of all conferences a person attended in a JSON list stored in
35.
by neunhoef 12y ago
Interesting article. An obvious reaction is to say: "In a document store, not all joins will be efficient in a sharding situation!". This is true, but certain queries involving joins backed by the right secondary indexes will inde
36.
by neunhoef 13y ago
Good arguments, I like in particular the insight that different business circumstances call for different database designs, and different compromises between consistency and availability. Google is of course a different player than most oth
37.
by neunhoef 13y ago
This is awesome. I like the way the vertices are automatically moved in a way such that they do not overlap very much and that the edges are easily visible. It is also good that "similar" vertices are automatically collapsed into
38.
by neunhoef 13y ago
Thanks, and: you are right, scaling by sharding is important, and that is why we have made this our top priority for the coming three months.
39.
by neunhoef 13y ago
I would call https://www.arangodb.org/manuals/current/UserManual.html a browsable doc (3 clicks from the main page). And a further click fires up the chapter about AQL...
40.
by neunhoef 13y ago
NOSQL databases in general (and multi-model databases like ArangoDB in particular) offer a greater flexibility in the choice of your data structures than traditional relational databases do. Furthermore, you can configure exactly the right
41.
by neunhoef 13y ago
The big advantage of ArangoDB with respect to memory/disk usage is that despite the Schema-less-ness, the database automatically recognises common "shapes" of the documents in a collection and thus usually does not have to st
42.
by neunhoef 13y ago
What do you think is the primary cause of excessive space usage in MongoDB?