是否有 NoSQL 解决方案的比较(在某些情况下哪个更好?)

Is there a Comparison of NoSQL Solutions (Which is better in certain situations?)(是否有 NoSQL 解决方案的比较(在某些情况下哪个更好?))

问题描述

我正在尝试了解有关 NoSQL 的更多信息，因为我正在 Linux/PHP 架构中构建基于密钥的归档应用程序.任何人都可以解释主要解决方案(CouchDB/MongoDB/等)之间的差异，以了解每个解决方案的优缺点吗?链接会很棒，虽然我很难单独使用 Google 进行研究.

I'm trying to learn more about NoSQL as I'm building a key-based archiving app in a Linux/PHP architecture. Can anyone explain the differences between the major solutions (CouchDB/MongoDB/etc) as to the advantages/disadvantages to each? Links would be great, though I'm having a hard time doing research using Google alone.

推荐答案

http://aphyr.com/tags/Jepsen 如果你想了解很多数据库如何处理网络问题，这个系列非常棒:

http://aphyr.com/tags/Jepsen this series is excellent if you want to see how a lot of databases handle network problems:

我们将了解分布式共识，讨论 CAP 定理的含义，并演示不同数据库在分区下的行为方式.

We're going to learn about distributed consensus, discuss the CAP theorem's implications, and demonstrate how different databases behave under partition.

这篇关于是否有 NoSQL 解决方案的比较(在某些情况下哪个更好?)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！