Its performance had a significant impact on our decision making as well. It sustains an enormous number of writes and the read cycle times were much better than we had anticipated. Further, it gives us the option to interact with the Hadoop Ecosystem, including HDFS, Mapreduce, and Zookeeper frameworks. Our enthusiasm for HBase skyrocketed when we discovered how to create map-reduce apps to do a number of management tasks. While Cassandra also has these capabilities, its data model was fundamentally more complex.
What if the whole post would have said: we chose HBase because of
- its seamless integration in the Hadoop ecosystem
- the scalable time series OpenTSDB is built on top of HBase?
Original title and link: Why We Chose HBase for AppFirst APM ( ©myNoSQL)