I've been using ArangoDB for a year now and I think they are definitely on to something cool.<p>Having stumbled upon some really complex data a few times now, I am increasingly appreciating how amazing it is to model your data any way you need, without having to deal with the complexity of running multiple data stores.<p>Cool to see that I apparently didn't give up any performance to get the flexibility. :)<p>I'd love to see them push the geospatial capabilities a little further, but they are already pretty decent.
This does not explain why arangodb is faster. Stating that «Native multi-model» is a killer feature would be more interesting if it was explained what it means outside of «arangodb=graph+k/v+document stores». What is the difference between a graph vertex without edge and a document at the storage level? arangodb is faster than wiredtiger? suspicious.
Never trust a benchmark.<p>>>The uncompressed JSON data for the vertices need around 600 MB and the uncompressed JSON data for the edges requires around 1.832 GB.<p>So why use a 60GB RAM machine for so little data?<p>Can we get some raw numbers instead of %?