The road to ACID transactions in Cassandra 6
theconsensus.dev
The road to ACID transactions in Cassandra 6
1–10 of 26 posts
Re: The road to ACID transactions in Cassandra 6
#2Thanks for this, really looking forward to the release of Accord
Re: The road to ACID transactions in Cassandra 6
#3I'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.
Re: The road to ACID transactions in Cassandra 6
#4I'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 f…
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.
Re: The road to ACID transactions in Cassandra 6
#5I'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 f…
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 vers…
Drop in with same schematics? It's not going to be easy, I don't have an answer. It's unpopular, but probably I'd architect my software more towards a sharded mongo cluster for write heavy workloads these days, rather than lean on cass/scylla/cockroach.
Mongo bit me a lot pre-wiredtiger and I refused to forgive them for years, but I'm using it again since 8.x and it's really... Boring, Scalable. There are many ways to skin a cat though, and I know not everyone has the luxury of redesigning their apps to fit the persistence layer.
Re: The road to ACID transactions in Cassandra 6
#6I'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 f…
I also run a large-ish cassandra cluster, and I dont really disagree, but then what else?
I would not recommend starting new projects with it either, but what else will you use?
Re: The road to ACID transactions in Cassandra 6
#7I'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 f…
I also run a large-ish cassandra cluster, and I dont really disagree, but then what else? I would not recommend starting new projects with it either, but what else will you use?
Wasn't ScyllaDB designed to be a drop in? The idea of running a Java or Golang DB sounds like fresh hell to me.
Re: The road to ACID transactions in Cassandra 6
#8Earlier quoted context omitted.
I also run a large-ish cassandra cluster, and I dont really disagree, but then what else? I would not recommend starting new projects with it either, but what else will you use?
Wasn't ScyllaDB designed to be a drop in? The idea of running a Java or Golang DB sounds like fresh hell to me.
Why is java bad here...? Because of GC?
Re: The road to ACID transactions in Cassandra 6
#9I'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 f…
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 vers…
i'd say 99% of usecases will be served fine with Postgres, or a managed instance via AWS
Re: The road to ACID transactions in Cassandra 6
#10Earlier quoted context omitted.
I also run a large-ish cassandra cluster, and I dont really disagree, but then what else? I would not recommend starting new projects with it either, but what else will you use?
Wasn't ScyllaDB designed to be a drop in? The idea of running a Java or Golang DB sounds like fresh hell to me.
yeah, i suppose one could start with scylladb as their base today.