NoSql 之战 - 幸存者？
GraphDB vs Key-ValueDb
Neo4j vs OrientDB Valdemort 与 OrientKV
可供选择和比较的功能
- 易于安装（无依赖性，只需在文件夹中放置/提取）
- 性能和可扩展性
- 占用空间小
- 良好的文档（教程和示例）
- 管理设施、监控工具
- 学习曲线低
- 与 java 或 ruby 的界面
有哪些赢家？
具有相同特性/功能的另一种选择？
GraphDB vs Key-ValueDb's
Neo4j versus OrientDB
Valdemort versus OrientKV
Features to choice and compare
- Easy to install (no dependencies, just place/extract on folder)
- Performance and scalability
- small footprint
- good documentation (tutorials and examples)
- administration facilities, monitoring tools
- low learning curve
- interface with java or ruby
What are the winners?
Another option with the same characteristics/features?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
那么文档数据库呢？我认为 mongo 是有史以来最伟大的东西
What about document databases? I think mongo is the greatest thing ever
我和史蒂夫·C 在一起。布偶赢了！实际上，我正在评估 Neo4j 和 OrientDB。倾向于 OrientDB，因为它的性能配置文件符合我的需要。
而不是看“金光闪闪”的数字，而是了解您的系统的读/写比率。是读多于写，还是搜索更重要？一旦你弄清楚了这一点，那么选择就变得容易了。
顺便说一句，Neo4j 和 OrientDB 都有很好的文档和示例。祝您一切顺利。
I'm with Steve C. The Muppets win! Actually, I'm evaluating Neo4j and OrientDB. Leaning to OrientDB because it's performance profile matches what I need.
Rather than look at the "bling" figure out what the read/write ratio will be for your system. Is it more read than write, or are searches more important? Once you've figured that out, then the selection becomes easier.
BTW Both Neo4j and OrientDB have good documentation and examples. All the best with your choice.
这不是您要寻找的获胜者。根据我的经验，理想的数据库类型是最适合您的应用程序的数据库类型。对于高级应用程序，您可能希望将对象绑定到数据库。最好的选择仍然是像 SQL 这样的关系数据库。它已经发展了20多年。适用于 SQL 的工具随处可见。 NoSql 数据库还很年轻，工具也很难找到。
我个人尝试过 Neo4j。我喜欢他们在 Neo4j 中使用的图形模型。它允许您向节点和关系添加属性。然而，用于查看图形或 NoSQL 数据库的工具远不如 SQL 表好。
对我来说，我发现纯文本文件或 xml 是适合我的大多数应用程序的最佳数据库。
It's not the winner that you are looking for. From my experience, the ideal type of databse is the one which is best for your application. For advanced application, you may want to have object binding to database. The best option of all is still relational database like SQL. It has been developed for more than 20 years. Tools are available for SQL everywhere. NoSql database is still young and tools are difficult to find.
I personally have a try with Neo4j. I love the graph model they use in Neo4j. It allows you to add attributes to node and relationships. However, tools for viewing the graph or NoSQL databse are not nearly as good as SQL table.
For me, I find plain text file or xml is the best database for most of my application.
我想说的最大区别是——可扩展性。 Neo4j 目前不支持集群。但你可以进行主从复制。不过OrientDB支持集群。
Neo4j 中每个节点的数据需要存储为键值对。使用 OrientDB，您可以将数据保存为文档，并且仍然可以具有类似图形的关系。 OriendDB 还支持 ACID。
The biggest difference I would say is - scalability. Neo4j doesn't support the cluster as of now. But you can have master slave replication. However OrientDB support cluster.
The data at each node needs to be stored as key-value pairs in Neo4j. With OrientDB you can save data as document and can still have graph like relationships. OriendDB also supports ACID.