在选择hbase之前应该考虑什么？ [英] what should be considered before choosing hbase?

问题描述

我们从团队得到了建议，我们应该使用hbase而不是RDBMS来获得高性能。在将RDMS切换到hbase之前，我们不知道应该/必须考虑什么。任何想法？

解决方案

来到@ Whitefret的最后一点：根据哪些决定可以采取，有一些东西叫做

• 一致性（所有节点在同时）
  

• 可用性（每个请求都会收到有关它成功还是失败的响应）

>

分区容忍（尽管由于网络故障导致任意分区，系统仍继续运行）

Hbase支持CP

但是，为了将RDBMS转换为HBASE，您可以使用 SQOOP 。

I am very new in big data space.

We got suggestion from team we should use hbase instead of RDBMS for high performance . We do not have any idea what should/must be considered before switching RDMS to hbase. Any ideas?

解决方案

One of my favourite book describes..

Coming to @Whitefret's last point : There is some thing called CAP theorm based on which decision can be taken.

• Consistency (all nodes see the same data at the same time)

• Availability (every request receives a response about whether it succeeded or failed)

• Partition tolerance (the system continues to operate despite arbitrary partitioning due to network failures)

In this context Hbase supports CP

However, for switching RDBMS to HBASE you can use SQOOP.

这篇关于在选择hbase之前应该考虑什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！