I would love to see a comparison between Arangodb and Rethinkdb, especially performance wise. Is it suitable for realtime applications? What language drivers are supported?
Claudius from ArangoDB here. Frank already answered a question about realtime queries below: "We are evaluating various possibilities, how to implement streaming queries in an efficient and scalable way. For instance, are restrictions to the general AQL necessary for such queries to be able to scale? Stay tuned."
Great news! We decided a couple of months ago to go with arangoDB, we have built already a 32Gb Graph Database and so far it has performed really well. It's easy to install and great as a first contact on the GraphDB world aside from Neo4J.
"The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate
directly or indirectly, or take a direct financial interest in, any Patent Assertion: (i) against Facebook or any of its subsidiaries or corporate affiliates," ... and so on.
I think that means that if my company goes after (in any way, shape or fashion) any Facebook patents, and we're using ArangoDB, we're instantly in copyright violation.
You don't lose your copyright license, you lose the patent grant. Most MIT/BSD licensed software doesn't come with a patent grant; many people assume that you get an implicit grant but that opinion will vary depending on which lawyer you talk to.
We have been using ArangoDB (2.8.x) for some time. Solid product with awesome support in Google group and SO. Great job guys! Looking forward to migrate to 3.x especially for the persistent index.
Awesome, I JUST started using ArangoDB for my latest project. So far so good, and these changes look solid. Only thing I wish they had(unless I'm missing something), is a GridFS type storage.
Pure curiosity, why do you miss GridFS? I think ArangoDB it already does that, back in time there was journal size setting, I'm not sure if it still has.
Congratulations! What a nice bunch of new features. Thinking all three models from the ground up has really payed off! Will check out the docker image soon...
Max from ArangoDB here. Just to avoid disappointment: The official Docker image arangodb will need a few days to be updated and be validated by Docker. Use arangodb/arangodb:3.0.0 in the meantime.
We are evaluating various possibilities, how to implement streaming queries in an efficient and scalable way. For instance, are restrictions to the general AQL necessary for such queries to be able to scale? Stay tuned.
Hi, I'm Frank from ArangoDB. You should create a number of shards that is much higher than your initial number of servers. ArangoDB can cope with multiple shards per server. This way, you can easily redistribute shards when adding new servers.
[+] [-] hexalisk|9 years ago|reply
[+] [-] don71|9 years ago|reply
Regarding performance, it would be great if somebody with excellent knowledge about rethinkdb would contribute to https://github.com/weinberger/nosql-tests
[+] [-] arthursilva|9 years ago|reply
[+] [-] pluma|9 years ago|reply
(I'm the lead developer of the new ArangoDB Foxx, AMA)
[+] [-] merqurio|9 years ago|reply
[+] [-] Diederich|9 years ago|reply
It apparently uses Facebook's RocksDB, which is also, I'm told, a pretty nice package. However, there is this:
https://github.com/facebook/rocksdb/blob/master/PATENTS
"The license granted hereunder will terminate, automatically and without notice, if you (or any of your subsidiaries, corporate affiliates or agents) initiate directly or indirectly, or take a direct financial interest in, any Patent Assertion: (i) against Facebook or any of its subsidiaries or corporate affiliates," ... and so on.
I think that means that if my company goes after (in any way, shape or fashion) any Facebook patents, and we're using ArangoDB, we're instantly in copyright violation.
Is this a roughly accurate assessment?
Thanks!
[+] [-] bryanlarsen|9 years ago|reply
[+] [-] reactor|9 years ago|reply
[+] [-] overcast|9 years ago|reply
[+] [-] janemanos|9 years ago|reply
[+] [-] merqurio|9 years ago|reply
[+] [-] sedlich|9 years ago|reply
[+] [-] neunhoef|9 years ago|reply
[+] [-] zimbatm|9 years ago|reply
[+] [-] fceller|9 years ago|reply
[+] [-] ralusek|9 years ago|reply
[+] [-] fceller|9 years ago|reply
However, in general it is more flexible and safer to use Foxx, because it allows you to fine tune complexes queries and supports transactions.
[+] [-] continuational|9 years ago|reply
[+] [-] fceller|9 years ago|reply
[+] [-] nrjames|9 years ago|reply
[+] [-] merqurio|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]