When we tell people that we’ve moved over 300 terabytes of Solana archival data off of ClickHouse and onto RocksDB, the reaction is almost always the same: Why would you ever do that?
ClickHouse is the obvious choice for petabyte-scale analytical workloads. RocksDB, on the other hand, is an embedded key-value store with sparse documentation, primarily used as the engine within other databases (e.g., CockroachDB, TiKV, MyRocks), rather than as the direct foundation for a customer-facing historical data service.
This article explains why we migrated from ClickHouse, what we learned about the workload along the way, and how we’re using RocksDB in production at scale.
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.