title: Cassandra vs Hbase for storing the events count for every user
body: <p>I was wondering whether we should use the Hbase or Cassandra for the following case : </p>
  
  <ol>
  <li><p>I need the event tracking for every customer. Which will store one
  row for a customer on a daily basis and next day will create another
  row for the same customer. But that row may get updated quite
  frequently in a day for a customer.  Now, when there are quite
  frequent updates on a table. </p></li>
  <li><p>In case of frequent updates data will get split in multiple
  SSTables. Which will lead to increase in latency while reading. What's the main purpose behind the counter in the cassandra?</p></li>
  <li><p>Also, in case of hbase there is a problem of single point of
  failure.</p></li>
  </ol>