Update Idempotency: Why It is Important in Cassandra Applications | Max's Output
When you develop application for Cassandra you should be aware of the following fact. Even when client observes the failure of an update it is still possible that this update has been executed successfully. The cause of such anomalous behavior is that Cassandra does not support transactional rollback. But please do not rush with judgements. There is a reason for that. Cassandra is a distributed database so rollback requires support for distributed transactions that have a performance cost and do not scale well. So if you want it fast and scalable you have to handle this anomaly.
Read full article from Update Idempotency: Why It is Important in Cassandra Applications | Max's Output
No comments:
Post a Comment