OrientDb or ArangoDb?
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
- OrientDb is buggy, to the extent that people have lost their data in production
- OrientDb team is focussed on getting more half-baked features out that are good for marketing but are full of bugs
- OrientDb team is slow at fixing critical issues
- They also tend to mark number of issues as "won't fix/non-issue" when the issues are actually a fault in OrientDb and are hurting the users
- Attitude of OrientDb team is "we do not welcome criticism"
Has anyone here experience of both OrientDb and ArangoDb? Which one will you recommend?