Compare Neo4j Graph Database and OrientDB 
- Users report that Neo4j Graph Database excels in its Ease of Setup with a score of 8.8, making it a preferred choice for those looking for a quick implementation. In contrast, OrientDB, while still decent, has a lower score of 8.2 in this area.
- Reviewers mention that Neo4j's Query Language is highly intuitive and user-friendly, scoring 8.6, which enhances the overall experience for developers. OrientDB, however, has a slightly lower score of 8.3, indicating that users may find it less straightforward.
- G2 users highlight Neo4j's superior Quality of Support with a score of 8.5, suggesting that users feel well-supported during their usage. Conversely, OrientDB's support quality is rated at 7.4, which may leave some users wanting more assistance.
- Reviewers mention that Neo4j shines in Data Management with a score of 9.0, indicating robust capabilities in handling complex data relationships. OrientDB, while still competent, scores 7.7, suggesting it may not be as effective in this critical area.
- Users on G2 report that Neo4j's Product Direction is highly rated at 9.0, reflecting a strong confidence in the product's future development. In contrast, OrientDB's score of 6.9 indicates some uncertainty among users regarding its ongoing evolution.
- Users say that Neo4j's Data Types support is rated at 8.7, which allows for a diverse range of data handling. OrientDB, while still offering good support at 8.2, may not provide the same level of flexibility as Neo4j.
- console.neo4j.io
I started using Neo4J to represent various facilities ( of a startup that I work at) across the city as nodes and represent their relationships in terms of mode of commute available and the associated costs. The brilliant thing about Neo4J, or graph DB...
The tooling itself was an issue. We used the neo4j ruby bindings to create an embedded neo4j database in rails. This required us to use jruby instead of regular ruby. Using jruby created a lot of other issues with compatibility with the various gems out...
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...
I started using Neo4J to represent various facilities ( of a startup that I work at) across the city as nodes and represent their relationships in terms of mode of commute available and the associated costs. The brilliant thing about Neo4J, or graph DB...
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...
The tooling itself was an issue. We used the neo4j ruby bindings to create an embedded neo4j database in rails. This required us to use jruby instead of regular ruby. Using jruby created a lot of other issues with compatibility with the various gems out...
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...
