HNHacker News
TopNewBestAskShowJobs

neunhoef

57 karma · joined December 6, 2013

[ my public key: https://keybase.io/neunhoef; my proof: https://keybase.io/neunhoef/sigs/lWPEMpv8NltDjZN5uS50zMQpOl-YuQl51ZZly4JLJ0w ]
submissionscomments
neunhoef··on Modeling Data in MongoDB vs. ArangoDB
Right, you were quicker but are essentially saying the same thing as I said in my example.
neunhoef··on Modeling Data in MongoDB vs. ArangoDB
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 an attribute with the user. A query finding all people with last name "Jones" that have attended a given conference can now be executed efficiently by using a secondary index on the last name of people and performing a key lookup in the conferences collection. The latter only has to talk to one shard, if the conferences collection is sharded by key and can thus be done efficiently. Obviously, one needs a query optimizer that is aware of the distribution of the shards and the shard keys, but this is certainly doable.
neunhoef··on Modeling Data in MongoDB vs. ArangoDB
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 indeed scale well, therefore one should not use this argument as a reason not to implement joins at all.
neunhoef··on CAP and Google Spanner: the survival of eventual consistency
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 others on this planet.
neunhoef··on ArangoDB
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 a "multi-vertex". I think this is very useful functionality to inspect a big graph locally.
neunhoef··on ArangoDB
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.
neunhoef··on ArangoDB
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...
neunhoef··on ArangoDB
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 compromise for your application between ACID and eventual consistency, and consistency/scalability.
neunhoef··on ArangoDB
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 store all attribute names many times. In addition, the possibility of transactions makes it less necessary to keep many old revisions of documents, in comparison to for example MongoDB.
neunhoef··on ArangoDB
What do you think is the primary cause of excessive space usage in MongoDB?
← PreviousPage 2 of 2