Hacker News new | past | comments | ask | show | jobs | submit login

I‘ve used Cassandra, its not that impressive. Much slower than the C++ rewrite (ScyllaDB?), latency issues due to GC, can’t hold a candle to Clickhouse. And they’ve been optimizing it for a long time now.



Cassandra and ClickHouse are designed to do different things. To flip things around, have you compared the latency of a single-row update or delete in Cassandra vs ClickHouse?


Or the fact that Cassandra uses consistent hashing to distribute data automatically across hosts.

My company supports ClickHouse, but there are many use cases where it's simply not the right solution.


If you care about the latency of a single row update or delete, Clickhouse is definitely the wrong tool for the job. First, it doesn’t really have deletes(afaik). Second, you need to batch updates aggressively to get good throughput.

But you’re right C* and CH are designed to do different things. I just found the difference in general performance across everything (startup, schema changes, throughput, query performance, optimization opportunities) to be quite pronounced. One feels like a race car, the other not so much.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: