I think the links provided are general comparison. I will try to explain the difference as I implemented time series with both Cassandra and HBase. We migrated from Cassandra to HBase. Reasons: Scan is fast with HBase. It fits better with time series data model. Please look at opentsdb. Cassandra models it with large rows. Server side filtering. You can use to filter some of your time series data on the server side. Hbase has a better integration with hadoop in general. We had to write our own bulk loader using mapreduce for cassandra. hbase has already had a tool for that. There is a nice integration with flume and kite. High availability didnet matter for us. 10 secs down is fine for our use cases.HBase started to support eventually consistent reads.
Cem Sent from my iPhone > On May 30, 2015, at 4:24 PM, Brady Gentile <br...@datastax.com> wrote: > > Hey Ajay, > > Here are some use cases from PlanetCassandra.org of companies who chose > Cassandra over HBase after evaluation, or migrated to Cassandra from HBase. > > The eComNext interview cited on the page touches on time-series data; if > you're interested in talking with Miguel Coira, I'd be happy to make that > connection. > > http://planetcassandra.org/hbase-to-cassandra-migration/ > > Brady Gentile > Program Manager > 480.735.1133 > > >> On May 29, 2015, at 12:09 PM, Ajay <ajay.ga...@gmail.com> wrote: >> >> Hi, >> >> I need some info on Hbase vs Cassandra as a data store (in general plus >> specific to time series data). >> >> The comparison in the following helps: >> 1: features >> 2: deployment and monitoring >> 3: performance >> 4: anything else >> >> Thanks >> Ajay
