Compare ArangoDB and OrientDB 
- Users report that OrientDB's Multi-Model support is rated at 9.3, which allows for flexibility in data representation, while ArangoDB's rating of 9.1 is slightly lower, indicating that OrientDB may offer a more robust multi-model experience.
- Reviewers mention that ArangoDB excels in Query Optimization with a score of 8.7 compared to OrientDB's 7.3, suggesting that users may experience faster query performance and efficiency with ArangoDB.
- G2 users highlight that OrientDB's Data Model is rated at 9.0, which is competitive, but ArangoDB shines with a score of 9.2, indicating a more advanced and versatile data modeling capability that could benefit complex applications.
- Users on G2 report that ArangoDB's Data Replication feature is rated at 8.5, which is higher than OrientDB's 8.1, suggesting that ArangoDB may provide more reliable data replication options for critical applications.
- Reviewers say that OrientDB's Ease of Use is rated at 7.7, which is lower than ArangoDB's 8.9, indicating that users may find ArangoDB more intuitive and user-friendly for everyday tasks.
- Users report that ArangoDB's Quality of Support is rated at 8.9, significantly higher than OrientDB's 7.4, suggesting that users may have a better experience with customer support and resources when using ArangoDB.
- Fully Managed: ArangoDB Oasis offers a fully-managed graph database, document store and full-text search engine. All in one place
- Highly Secure: Encryption at transit & at rest guarantee all your data is encrypted before it hits the disk or send over the network. In addition, you can assign fine-grained access control policies to your organization, your projects or deployments. This assigns permissions to groups or individual users
- Elastic Scale: You can elastically scale with all deployment models (OneShard & Sharded Clusters) at anytime and use the special Enterprise features for efficient queries against distributed data
Having the option for combined graph and document store was just what we needed. We were replacing a Mysql implementation of our product. Replacing the iterative collection of data with a graph traversal improved performance 1000x. The document store...
No ANSI SQL support, I was hopping for SQL support, that was a disappointing thing to learn a new language. We use CQL at the moment, Spark SQL, and SQL on MySQL, now we have to adapt to AQL which is an unnecessary overhead in my opinion.
1. Elaborated documents for a beginner without any graph background knowledge to grasp basic graph theory and orientdb practice. 2. Build on Java platform, which is our company's main dev language as well, it's too easy to spend much time customizing...
Documentation touches most topics, but it does not go into enough detail in almost all cases and there are way too few examples. The OrientDB team really needs to put more resources into documentation and code examples. Also, there is a lot of work to be...
Having the option for combined graph and document store was just what we needed. We were replacing a Mysql implementation of our product. Replacing the iterative collection of data with a graph traversal improved performance 1000x. The document store...
1. Elaborated documents for a beginner without any graph background knowledge to grasp basic graph theory and orientdb practice. 2. Build on Java platform, which is our company's main dev language as well, it's too easy to spend much time customizing...
No ANSI SQL support, I was hopping for SQL support, that was a disappointing thing to learn a new language. We use CQL at the moment, Spark SQL, and SQL on MySQL, now we have to adapt to AQL which is an unnecessary overhead in my opinion.
Documentation touches most topics, but it does not go into enough detail in almost all cases and there are way too few examples. The OrientDB team really needs to put more resources into documentation and code examples. Also, there is a lot of work to be...
