4 ms·
> Cassandra has basically one usecase: high volume writes, with a few batch reads. That's how we use it in BigCompany(tm). Cassandra holds (almost) all of our
by Uberphallus 6y ago
> Cassandra has basically one usecase: high volume writes, with a few batch reads.
That's how we use it in BigCompany(tm).
Cassandra holds (almost) all of our data. Most of it comes from batch insertions, but more complex (and lower volume) data comes from various REST APIs we expose and other teams use.
Most reads (60%) done on it are boring batch reads: analytics, reports, deltas, etc.
For more complex reads (30%) we copy relevant rows to Hive tables, then perform queries there without dealing with partition key shenanigans. So, batch with extra steps.
Then anything that requires random reads (10%) is read from ElasticSearch:
1. Coming from REST backend if it's time sensitive.
2. Coming from a batch that reads from Cassandra if not.