We are looking to adopt a multi-model database approach for some of the projects we do. We have spiked ArangoDb and have really liked it. We are yet to spike OrientDb. Some of us are impressed with OrientDb as it has list of some cool features that Arango lacks and OrientDb is generally good at marketing and putting it in front of decision makers nicely.
My concerns around OrientDb are as below. These are mainly found from a series of blog posts by a disgruntled OrientDb user
Has anyone here experience of both OrientDb and ArangoDb? Which one will you recommend?
I've been working with ArangoDB for the last several weeks and love it. I'm writing a .NET Identity provider for it that's working great so far. ArangoDB + Azure has been heaven.
I've read online; the issues about OrientDB
Were using ArangoDB for 10 months
I've personally submitted at least 3 bugs, and other issues during this period
The team is responsive, and they try their best to resolve the issues
But there are still some bugs that they delay fixing them
You should be reading the open issues to avoid these bugs
Some of them that I can remember:
1- Do Not use "global" object in Foxx Services! You can FU** the whole DBMS
2- You Can't Have different databases with the same collection names and document keys, it causes DATA LOSS (e.g. DB A and B, both have a collection named "users", in both collections; exists a document with key 12, this causes the problem)
Denny Trebbin
Lead Fullstack Developer. Experimenting with bleeding-edge tech. Irregularly DJ. Hobby drone pilot. Amateur photographer.
Stick with ArangoDB.
You have already a good list of cons to not go with OrientDB.