HBase 单表随着数据量增大，会触发自动分区，导致写入性能下降，需要通过建表时指定预分区来解决，调整起来很麻烦，需要重新建表生效 ...

总结起来，HBase 并不是知乎在当前业务场景下的最优解。 事实上，即使知乎团队在非常努力的调优、优化的情况下，HBase 的响应时间仍然一直在剧烈波动。 而知乎团队不仅希望响应时间尽可能低，还希望它能够稳定，这一点 HBase 满足不了。 自建 RBase ...

Getting HBase to run directly on S3 would avoid all those issues. As a strategic customer with a strategic project to both parties, FINRA got Amazon's support to do the port.

HBase is an open-source, distributed, column-oriented store modeled after the Google paper, "Bigtable: A Distributed Storage System for Structured Data" by Chang et al.

HBase documentation proclaims that an HBase database should have hundreds of millions or — even better — billions of rows. Anything less, and you’re advised to stick with an RDBMS.

HBase was configured with native LZO and Cassandra with Google’s Snappy compression codecs. Although the computation ran longer, the compression reduces the number of bytes read from the disk.

HBase (structured storage for large tables) Cassandra (multi-master database) Of course, it’s not always sunshine and roses with this type of solution. Lam says the main pitfalls have to do with ...