blocks|key|4458207|text|Here's+Facebook's+original+post解释了为什么他们选择HBase作为Messenger。当时，他们认为HBase“在规模和性能方面是理想的，而且一致性尽可能接近‘即时’”，然而他们达到了它的极限，后来developed+a+new+service+called+Iris处理最近一周的消息，同时将较旧的消息存储在HBase中。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4458208|Cassandra's+consistency+model+provides+a+lot+of+flexibility。最大的区别是Cassandra是一个无共享架构:每个服务器都被设计为能够独立运行，因此具有高可用性和分区容错性，但代价是一致性。|4458209|然而，对于HBase，只有一个事实来源，那就是可用性和分区容错性的(明显)代价。从客户端的角度来看，读取过程包括找到数据的位置并从该服务器读取数据。对该数据的任何更新都是原子的。|4458210|Here's+one+HBase+vs+Cassandra+benchmark显示HBase在(大部分)默认设置上几乎在每一项测试中都优于卡桑德拉，here's+another+benchmark显示卡桑德拉在某些测试中表现优于HBase。我认为这里的结论是你的问题的答案很大程度上取决于你的用例。|4458211|Here's+a+good+article总结了每种方法的优缺点，可以帮助您决定哪种方法最适合您的需求。|4458212|entityMap|0|LINK|mutability|MUTABLE|url|https://www.facebook.com/notes/facebook-engineering/the-underlying-technology-of-messages/454991608919/|1|https://code.facebook.com/posts/820258981365363/building-mobile-first-infrastructure-for-messenger/|2|https://docs.datastax.com/en/cassandra/3.0/cassandra/dml/dmlConfigConsistency.html|3|https://hortonworks.com/blog/hbase-cassandra-benchmark/|4|https://jaxenter.com/evaluating-nosql-performance-which-database-is-right-for-your-data-107481.html|5|http://bigdatanoob.blogspot.com/2012/11/hbase-vs-cassandra.html^0|0|V|0|36|Z|1|0|0|1N|2|0|0|0|13|3|22|O|4|0|0|L|5|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]|$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|F|3|G|5|6|7|1E|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|1F|8|@]|9|@$A|1G|B|1H|1|1I]|$A|1J|B|1K|1|1L]]|C|$]]|$1|J|3|K|5|6|7|1M|8|@]|9|@$A|1N|B|1O|1|1P]]|C|$]]|$1|L|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]|V|$5|O|P|Q|C|$R|W]]|X|$5|O|P|Q|C|$R|Y]]|Z|$5|O|P|Q|C|$R|10]]|11|$5|O|P|Q|C|$R|12]]]]

<a href="https://www.facebook.com/notes/facebook-engineering/the-underlying-technology-of-messages/454991608919/" rel="nofollow noreferrer">Here's Facebook's original post</a> on why they chose HBase for Messenger. At the time they decided HBase was "ideal for scale and performance with consistency as near as possible to 'immediate'", however they reached its limits and later <a href="https://code.facebook.com/posts/820258981365363/building-mobile-first-infrastructure-for-messenger/" rel="nofollow noreferrer">developed a new service called Iris</a> that handles the most recent week of messages, while storing the older messages in HBase.

<a href="https://docs.datastax.com/en/cassandra/3.0/cassandra/dml/dmlConfigConsistency.html" rel="nofollow noreferrer">Cassandra's consistency model provides a lot of flexibility</a>. The biggest difference is that Cassandra is a shared-nothing architecture: each server is designed to be able to function independently, thus high availability and partition tolerance at the cost of consistency.

With HBase however there is a single source of truth, at the (apparent) cost of availability and partition tolerance. The read process, from the client's perspective, involves finding the location of that data and reading it from that server. Any updates to that data are atomic.

<a href="https://hortonworks.com/blog/hbase-cassandra-benchmark/" rel="nofollow noreferrer">Here's one HBase vs Cassandra benchmark</a> that shows HBase outperforming Cassandra on nearly every test on (mostly) default settings, and <a href="https://jaxenter.com/evaluating-nosql-performance-which-database-is-right-for-your-data-107481.html" rel="nofollow noreferrer">here's another benchmark</a> that shows Cassandra outperforming HBase on certain tests. I think the conclusion here is that the answer to your question is highly dependent on your use case.

<a href="http://bigdatanoob.blogspot.com/2012/11/hbase-vs-cassandra.html" rel="nofollow noreferrer">Here's a good article</a> that sums up the plusses and minuses of each, and can help you decide which one is best for your needs.

How is Cassandra's eventual consistency model different from HBase? It seems Facebook moved from Cassandra to HBase because consistency issues. Which of these NoSQL DBs are ideal for scale and performance with consistency as near as possible to 'immediate'. What is the factor by which performance degrades when we try to improve upon consistency?

Cassandra vs HBase Consistency Model

SQL数据库

数据库

服务器

Cassandra

HBase

NoSQL

卡桑德拉的最终一致性模型与HBase有何不同？似乎Facebook从Cassandra迁移到HBase是因为一致性问题。这些NoSQL数据库中的哪一个是可扩展性和性能的理想选择，并且一致性尽可能接近“即时”。当我们试图提高一致性时，性能下降的因素是什么？

问Cassandra vs HBase一致性模型
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Cassandra vs HBase一致性模型EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Cassandra vs HBase一致性模型
EN