Last time I looked at TimescaleDB a few months ago, it appeared to me that you had to ingest data into what they call an access node, which made it a non-starter for our use case, but matched perfectly with ClickHouse,…
Hmm, considering after 2 years of shipping Druid as part of a big data analytics product, my company is moving off of Druid because of performance and stability issues, I don't think my company, at least, would consider…
I have worked with Druid and ClickHouse extensively in the past year. I do think rebalancing is a weak point for ClickHouse, although for our use case that would not be so much of an issue, and it feels like it is on…
At the end of 2018 Altinity benchmarked ClickHouse against the TSBS and documented it. https://www.altinity.com/blog/clickhouse-for-time-series
I'll second Simplicity and add in that ClickHouse is also faster on less hardware and more stable compared to our current Druid configuration. My company currently uses Druid and has for a few years now, but I have been…
Last time I looked at TimescaleDB a few months ago, it appeared to me that you had to ingest data into what they call an access node, which made it a non-starter for our use case, but matched perfectly with ClickHouse,…
Hmm, considering after 2 years of shipping Druid as part of a big data analytics product, my company is moving off of Druid because of performance and stability issues, I don't think my company, at least, would consider…
I have worked with Druid and ClickHouse extensively in the past year. I do think rebalancing is a weak point for ClickHouse, although for our use case that would not be so much of an issue, and it feels like it is on…
At the end of 2018 Altinity benchmarked ClickHouse against the TSBS and documented it. https://www.altinity.com/blog/clickhouse-for-time-series
I'll second Simplicity and add in that ClickHouse is also faster on less hardware and more stable compared to our current Druid configuration. My company currently uses Druid and has for a few years now, but I have been…