Highlighting HBase's missing functionalities, the authors mention that the lack of distributed transactions in HBase led to several bugs and incidents for the in-house graph service.

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 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 ...