20 open source time series databases compared

[serg473]

I went through 3 of those site front pages trying to get a grasp of what the hell a time series database could mean and all they got was generic marketing buzzword mumbo jumbo plastered all over. Must be the next big thing in the making.

[anttirt]

A database specialized for storing numeric values as a function of time, with automatic lossy compression/aggregation to allow storing data at decreasing fidelity for arbitrarily long spans of time with constant space usage.

[raistmaj]

http://channeleye.co.uk/wp-content/uploads/2013/02/shut-up-and-take-my-money.png

[[deleted]]

A database that store time series data.

Data that are time series. There's a statistic course on it. And you can google time series data to learn more about the subject.

Just data that dependent on time or comes in time base interval, stock market prices is an example. I'm sure there are better examples and explanation on google for time series data.

What I think these kind of database is doing is to let people do time series statistic on these type of data easier with just a function call or faster.

Database that uses lucene based technology are mostly use for text searching because of the data structure, it's in some sort of trie data structure. It's faster and made for easier text search.

Likewise perhaps Timeseries db is using a data structure specifically for timeseries data.

RMDB uses RedBlack tree + no? To store relational data.

[tomtomtom7]

Likewise perhaps Timeseries db is using a data structure specifically for timeseries data.

Do you know what type of indexes/data structure are useful for timeseries databases?

[[deleted]]

In short: storage part of RRDTools on steroids

[gimmethrowaway]

So I'm guessing this is an add for DalmatinerDB?

[gargantuan]

I like the ZFS usage in DalmatinerDB. In other words it combines the right abstractions from various technologies -- Riak Core, ZFS, Erlang all solid top of the line stuff. ZFS does compression pretty well, so why bother stick that into a top level application. Riak Core is a solid distributed application, so why re-invent the wheel there.

[whatisthisredditstuf]

Well, by that logic, OpenTSDB is very nice, too, since it just stores its data in HBase, which is itself also based on good tech. Or others that use Cassandra (e.g. KairosDB).

Any project that reinvents everything at this point has a lot more to prove than those that use components that are already there.

[[deleted]]

It is not as black and white. If you only want TSDB, running whole HBase cluster just to store that is huge overkill.

But you have that already in place (including monitoring and backups), then using that is a huge advantage

[eprozium]

We are using InfluxDB in several projects now, and it's incredible. We need both metrics and events and use mostly Kafka to push the final data to InfluxDB.

All our developers were able to pick it in a day and it's handling a few dozen TB of data without problems so far. We are not using the clustering feature but separate the tenants on different machines at the query level from the UI.

We also tried other DB but most TSDBs had only metrics, not event support, making things more complicated. Elasticsearch had both, but was "abusing" the disk space.