Hacker News Reader

For a user perspective, you can also check out this recent blog: https://clickhouse.com/blog/hifis-migration-from-bigquery-to...

TL;DR * HiFi moved because BQ pricing and query latency did not fit the needs for their customer-facing app (music royalty data analytics) * Caveat when moving to ClickHouse: they had to adjust how they handle JOINs

Disclaimer: I also work at ClickHouse.

View on HN

> a single HIFI Enterprise account can easily have half a gigabyte of associated royalty data representing over 25 million rows of streaming and other transaction data

Curious about why they were struggling with this workload on BigQuery. It just doesn’t seem like very much data. Maybe they were cost-constrained and using a tiny slot reservation?

Reply on news.ycombinator.com