Cassandra适合写入和少读,HBASE随机读取写入 [英] Cassandra good for write and less read , HBASE random read write

查看:579
本文介绍了Cassandra适合写入和少读,HBASE随机读取写入的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Cassandra是否适合写入和少读,而HBASE适合随机读取和写入?听说Facebook用HBASE替换了Cassandra

是:fb开始构建Cassandra,把它放到OpenSource中,稍后再迁移到HBase。
我不确定为什么,但Cassandra和HBase都是很好的解决方案。



Cassandra的好处是
+ HA(没有SPOF),
+具有可调整一致性,
+写入速度快于读取速度(两者速度相当快)
- 但Cassandra可能会增加网络流量,因为协调节点必须与目标节点通信。
- Cassandra是自己的数据存储,而HBase默认使用HDFS。我强烈地认为这是切换的原因,因为fb有大量的数据,而且他们用较少的开销来分析它 - 但是带有单点故障。



当强一致性是强制性的时,HBase优于
+并且
+ Hadoop集成
- 但HMaster是SPOF

是的:Cassandra很快速顺序写入批量数据并顺序读取它们。由于HDFS,HBase非常擅长随机IO。在性能比较中,Cassandra的吞吐量一般稍快一些; HBase在延迟时间稍快。
从运营的角度来看,Cassandra非常易于维护,因为它非常可靠并且具有强大的系统架构。由于HMaster和所需的Zookeeper集群需要,HBase很难设置,因此不太健壮。

所以最终它完全取决于你的问题。我从来没有想过任何人避开卡桑德拉;所以我认为HBase更好。

Is it right that Cassandra is good for write and less read, whereas HBASE is good for random read and write? Heard that facebook replaces Cassandra with HBASE

解决方案

Yes: fb started building Cassandra, put it OpenSource, and migrated to HBase later on. I'm not exactly sure why but Cassandra and HBase are both good solutions.

Cassandra has benefits being + HA (no SPOF), + having tunable Consistency, and + doing writes faster than reads (both are rather fast) - But Cassandra may increase network traffic as coordinator nodes have to communicate with target nodes. - Cassandra does it's own data storage whereas HBase uses HDFS by default. I strongly assume this was the reason to switch because fb has massive amounts of data and with HBase they analyze it with less overhead -- but with a Single Point of Failure.

HBase excels + when strong Consistency is mandatory and + Hadoop integration - But HMaster is a SPOF

Yes: Cassandra is very fast writing bulk data in sequence and reading them sequentially. HBase is very good at random IO because of HDFS. In performance comparisons Cassandra is in general slightly faster in throughput; HBase is slightly faster at latency. From operations perspective is Cassandra very easy to maintain as it is very reliable and a robust systems architecture. HBase is hard to setup and less robust because of HMaster and the by standing Zookeeper cluster needed.

So in the end it's totally up to your problem. I never heart anybody avoiding Cassandra; so I think HBase was just better.

这篇关于Cassandra适合写入和少读,HBASE随机读取写入的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆