Most products in this space are pretty obtuse, so I'm excited about TimescaleDB because of the people who started it and the tech it's built on. I was really underwhelmed by problems with Influx, and I don't think this group and this tech will have the same class of issues.
I think HBase is better than Cassandra for this workload, and I generally like its design sensibilities and consistency focus (gross oversimplification C* = MySQL, HBase = pgsql?) . OpenTSDB is one of the more mature scale out timeseries DBs and works with both. It works pretty well, but getting a production quality HBase setup is non-trivial. OpenTSDB has some decent built in aggregation and filtering functions, but queries over long time spans are quite slow because it has to pull all the data out of HBase and into the tsd daemon.. that can be fixed with what HBase calls a co-processor (think stored procedure in SQL) but it hasn't been done yet.
So, I think TimescaleDB is hitting a real need at the right time, and seeing how expressive and easy to reason those queries are, I am excited to give it a shot.
I think HBase is better than Cassandra for this workload, and I generally like its design sensibilities and consistency focus (gross oversimplification C* = MySQL, HBase = pgsql?) . OpenTSDB is one of the more mature scale out timeseries DBs and works with both. It works pretty well, but getting a production quality HBase setup is non-trivial. OpenTSDB has some decent built in aggregation and filtering functions, but queries over long time spans are quite slow because it has to pull all the data out of HBase and into the tsd daemon.. that can be fixed with what HBase calls a co-processor (think stored procedure in SQL) but it hasn't been done yet.
So, I think TimescaleDB is hitting a real need at the right time, and seeing how expressive and easy to reason those queries are, I am excited to give it a shot.