OpenTSDB – A Distributed, Scalable Time Series Database

Re:OpenTSDB – A Distributed, Scalable Time Series Database by willempienaar on Monday December 21, 2015 @11:38PM (#10775857)

If you were to create an application that relies heavily on a time series database, what would you recommend?

I'm writing an application of this sorts, and my requirements won't be too bad (about 1000-4000 metrics on a per second basis). I will also rely heavily on predefined queries (rollups to 10s, 1m, 10m, 1h, etc.).

I'm hesitant to use OpenTSDB because the community "buy-in" seems to be going down.

EDIT: I can't lose data to downsampling. I will need to store this for both troubleshooting and regulatory purposes.

[ Parent | on HN ]

Re:OpenTSDB – A Distributed, Scalable Time Series Database by Cidan on Tuesday December 22, 2015 @12:01AM (#10775926)

I wouldn't worry too much about what the community thinks. TSDB fits the bill and works great. That being said, I've also heard wonderful things about druid.io (http://druid.io/), however I've yet to personally try it. We're going to start testing and throwing data at druid early next year though.

[ Parent | on HN ]

Re:OpenTSDB – A Distributed, Scalable Time Series Database by sdhsdh on Monday December 21, 2015 @11:43PM (#10775870)

If it's just a few streams at high frequency, my take would be to bucket it (eg every second or something) and stick it on your favorite database. You could use postgres arrays, the json columntype, or frankly just a blob in those rows containing all the data for a second.

You can then write some simple postgres queries to create the views your talking about and won't have to mess with any of the "look what I wrote last week" "databases".

[ Parent | on HN ]