Hacker News new | ask | show | jobs
by ksajadi 6 days ago
For our metrics and autoscaling engine at Cloud 66, we went through 5 iterations before settling on Clickhouse: 1. Redis 2. Cassandra 3. Handrolled: Ruby + RabbitMQ 4. Handrolled: Go + RabbitMQ 5. Clickhouse

Every time we reached some limit or huge optimization burdens that were unfeasible. Clickhouse has been rock solid for the past 4 years.

1 comments

I am having a hard time picturing what could be the problem that you were solving.

Redis, Cassandra, RabbitMQ and Clickhouse. RabbitMQ looks like a black sheep in this lineup.

Also like redis and clickhouse are diametrically different platforms. Wild to go from one to the other.
I’m gonna guess that it’s because Ruby is dog slow and not concurrent.