So you can do this with Cassandra, but you need more logic in your code.
Basically, you get the last safe number, M, then get N..M, if there are any
gaps, you try again reading those numbers. As long as you are not over writing
data, and you only update the last safe number after a successful
You might consider a hybrid solution with a transactional db for all data
that should be ACID complient and Cassandra for the huge amounts of data
you want to store.
2011/12/27 Radim Kolar h...@sendmail.cz
makes me feel disappointed about consistency in Cassandra, but I wonder is
there is a
makes me feel disappointed about consistency in Cassandra, but I wonder is
there is a way to work around it.
cassandra is not suitable for this kind of programs. CouchDB is slightly
better, it has transactions but no locking and i am not sure if
transaction isolation is supported now. mongodb
But is there any way of implementing minimum required ACID subset on
top of Cassandra?
try this, its nosql ACID compliant. I haven't tested this, it will have
most likely pretty slow writes and lot of bugs like any other oracle
application.
Hello everybody.
I am developer of financial-related application, and I'm currently evaluating
various nosql databases for our current goal: storing various views which show
state of the system in different aspects after each transaction.
The write load seems to be bigger than typical SQL
