TSDB vs HBase : What to choose in long term?

Question

The problem we are trying to solve: Store all the data points that could be queried later point to deduce the performance of a web service. Give a visual representation of data.

Here is my understanding so far from what I have read on Hbase and on TSDB sites

• TSDB stores data in Hbase, albeit in a little non-standard way (wide-row format)

• TSDB is blazingly fast and gives ways of adding graphs very quickly.

• HBase while slow compared to TSDB, gives you the option of using SIMBA ODBC driver to connect it to Tableau, which is amazingly agile and beautiful visual data-representation.

One more issue with TSDB is it doesn't work with current HBase .96 (I know tsuna@ is working on it but I don't have a timeline for a stable release of tsdb which works against current Hbase.96)

So your simple answer could be Hbase or TSDB, or in addition to choosing one over another, you can justify your answer and help me choose one over another.

I am open to other solutions if they can support about trillion data-points stored over a year.

Answer 1

• If you need plot data, you should consider using OpenTSDB. 

• OpenTSDB is continuously developing and in November it was released the RC 2.0 version. As database, there is also a fork of OpenTSDB called KairosDB and it uses Apache Cassandra. so that, while Opening TSDB allows you to store points up to seconds, you can store points up to milliseconds, 

• Timeseries Distributed Databases like OpenTSDB/KairosDB is better for plotting data in a quite simple way. When we look at the long term issue, maybe something better could be developed over Hbase because of its open-source nature.