m3

Excited to be able to share this with everyone today! A lot of hard work has gone into getting M3 to 1.0, so this represents a major milestone. In getting to this point, we've focused quite a bit on stability and resilency, performance improvements (most notably during bootstrapping), and ease of configuration. All of these changes are aimed at ensuring M3 provides you the bulletproof, high performance experience one would expect of a production grade metrics engine. For more information on what went into the release, take a look at the changelog (https://github.com/m3db/m3/releases/tag/v1.0.0). Thank you to the open source community and everyone who has been involved in getting M3 to 1.0! We're very excited for M3's future!

There are other time series databases worth comparison with TimescaleDB: * InfluxDB - https://www.influxdata.com/ * VictoriaMetrics - https://github.com/VictoriaMetrics/VictoriaMetrics/ * M3DB - https://github.com/m3db/m3/

I suggest checking out M3DB[1]. My team & I use it to serve metrics for all of Uber, we have ~1500 hosts across various clusters. It's serving us quite well. [1]: https://github.com/m3db/m3

Yes I've seen that also work, it's a lot of stitching together things yourself and we had to put a lot of caching in front of the inverted index we were using, however definitely plausible. ClickHouse doesn't do any streaming of data between nodes as you scale up and down which was a big thing for us since we had large datasets and needed to rebalance when cluster expanded/shrunk. With regards to trie vs inverted index for Graphite data, I'd actually still be inclined to say inverted index is better based on the amount of queries I saw at Uber with Graphite where people did `servers.*.disk.bytes-used` type queries which is way faster to do using an inverted index since you have a postings list for each part of the dot-separated metric name, rather than traversing a trie with thousands to tens of thousands of entries in index 1 host part

Chronosphere, a startup founded by two of the early M3 engineers, just raised 11 million dollars to build a monitoring platform based around M3DB: https://techcrunch.com/2019/11/05/chronosphere-launches-with... Uber also uses M3DB extensively internally and the project is nowhere near being abandoned or on life support: https://github.com/m3db/m3/commits/master