Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Rise of Open Source Time Series Databases

victoriametrics.com

Post reply on HN
Print view View original

31–40 of 71 posts

Re: The Rise of Open Source Time Series Databases

#31

Post by peteforde »

If the author ends up reading this... as someone who is ignorant but curious about time series databases, it was frustrating to see an example of what relational data looks like, but then no example of what time series data looks like.

It might take a bit more context or setup, but this article is an opportunity to educate folks who aren't deep in the same trench.

Edit: in fairness, this article doesn't describe itself as "a Postgres developer's guide to getting started with time series databases" and maybe that's what I was unfairly hoping I would find.

Re: The Rise of Open Source Time Series Databases

#33

Post by osigurdson »

peteforde wrote: post #31

If the author ends up reading this... as someone who is ignorant but curious about time series databases, it was frustrating to see an example of what relational data looks like, but then no example of what time series data looks like. It might take a bit more context or setup, but this article is an opportunity to educate folks who aren't deep in the same trench. Edit: in fairness, this article doesn't describe itse…

The naive relational time series table looks like:

propertyid, timestamp, value

Then add a covering index so your reads only ever hit the index. This works completely fine for low billions of rows. After that suggest using clickhouse. It is less general but at large enough scale you need to make some tradeoffs. Completely fine to start with a relational DB in many cases though.

Re: The Rise of Open Source Time Series Databases

#34

Post by IOT_Apprentice »

PeterZaitsev wrote: post #21
Mongoose wrote: post #17

Had me until claiming that InfluxDB was the first mainstream TSDB in 2013 . OpenTSDB (2010)? Graphite (2008)? RRDtool (1999)? Maybe Influx took off in a way these prior projects didn't, but people have been storing time series data for decades.

I think While OpenTSDB was reasonably general purpose, Graphite and RRDTools were done for very specific monitoring use cases.

We used a customized version of OpenTSDB at eBay to do monitoring of everything on the platform, including the search infrastructure. This was during the time eBay built a private cloud.

Re: The Rise of Open Source Time Series Databases

#35

Post by osigurdson »

Mongoose wrote: post #17

Had me until claiming that InfluxDB was the first mainstream TSDB in 2013 . OpenTSDB (2010)? Graphite (2008)? RRDtool (1999)? Maybe Influx took off in a way these prior projects didn't, but people have been storing time series data for decades.

InfluxDB always seemed like it was run by children who are good at raising VC money.

Re: The Rise of Open Source Time Series Databases

#37

Post by candiddevmike »

osigurdson wrote: post #35
Mongoose wrote: post #17

Had me until claiming that InfluxDB was the first mainstream TSDB in 2013 . OpenTSDB (2010)? Graphite (2008)? RRDtool (1999)? Maybe Influx took off in a way these prior projects didn't, but people have been storing time series data for decades.

InfluxDB always seemed like it was run by children who are good at raising VC money.

Eventually one of their rewrites will find product market fit.

Re: The Rise of Open Source Time Series Databases

#38

Post by candiddevmike »

osigurdson wrote: post #33
peteforde wrote: post #31

If the author ends up reading this... as someone who is ignorant but curious about time series databases, it was frustrating to see an example of what relational data looks like, but then no example of what time series data looks like. It might take a bit more context or setup, but this article is an opportunity to educate folks who aren't deep in the same trench. Edit: in fairness, this article doesn't describe itse…

The naive relational time series table looks like: propertyid, timestamp, value Then add a covering index so your reads only ever hit the index. This works completely fine for low billions of rows. After that suggest using clickhouse. It is less general but at large enough scale you need to make some tradeoffs. Completely fine to start with a relational DB in many cases though.

But then I have to use standard SQL instead of a vendor's half assed, poorly documented query language.
Post reply on HN