I'm sure for some workloads, cassandra is 'ideal' or at least was 10 years ago.
What I can say though (as someone running thousands of cpus worth of cassandra at the moment); is that I deeply dislike this database. It's an operational nightmare, and I will not miss it even the slightest bit if it goes away forever.
On the other hand, I'm sure glad to see a bit of life in cassandra dev, it seems to have been dormant for a while; but would I pick it for new applications in 2026? No. I'd strongly recommend against using it unless you have the money to pay for a dedicated team to maintain it, and even then just.. No.
heipei [3 hidden]5 mins ago
So what is the alternative? It took me a while to get around the data schema / modelling that a database like Cassandra imposed, but when it finally clicked it really clicked for me, so much so that I wish I could have the same performance footprint of consistent hashing / sharding with other databases.
We are using ScyllaDB, but since they discontinued their Open Source version we're stuck on the last supported version, and reading about the operational headaches of Cassandra does not inspire confidence to give it a go.
javier2 [3 hidden]5 mins ago
Thanks for this, really looking forward to the release of Accord
HN.zip
What I can say though (as someone running thousands of cpus worth of cassandra at the moment); is that I deeply dislike this database. It's an operational nightmare, and I will not miss it even the slightest bit if it goes away forever.
On the other hand, I'm sure glad to see a bit of life in cassandra dev, it seems to have been dormant for a while; but would I pick it for new applications in 2026? No. I'd strongly recommend against using it unless you have the money to pay for a dedicated team to maintain it, and even then just.. No.
We are using ScyllaDB, but since they discontinued their Open Source version we're stuck on the last supported version, and reading about the operational headaches of Cassandra does not inspire confidence to give it a go.