官术网_书友最值得收藏!

Lightweight transactions

As discussed before, Cassandra provides eventual consistency rather than immediate consistency, which means data written will eventually be consistent across multiple replicas of the data. This has implications on the data returned by read queries. There is a possibility that reads could return stale data depending on how writes and reads are configured (the consistency levels at which both queries are performed). Strong consistency, which means reading the most recently written value, can be achieved using quorum reads and writes. But what if strong consistency is not enough? What if we have some operations to perform in sequence that must not be interrupted by others, that is, we must perform them one at a time, or make sure that any that we do run concurrently get the same results as if they really were processed independently. Cassandra provides lightweight transactions with linearizable consistency to ensure a transaction isolation level similar to the serializable level offered by RDBMSs. They are also known as compare and set transactions. You can use lightweight transactions instead of durable transactions with eventual/tunable consistency for situations that require the nodes in the distribution system to agree on changes to the data.

主站蜘蛛池模板: 巩义市| 泸定县| 临颍县| 疏勒县| 应用必备| 琼海市| 柘城县| 蒙城县| 定边县| 石台县| 祥云县| 福建省| 丽江市| 漠河县| 玛多县| 宁海县| 曲水县| 龙江县| 扶沟县| 乐东| 古丈县| 仙游县| 宁都县| 南丹县| 乾安县| 沭阳县| 吴旗县| 万州区| 托克逊县| 东丽区| 乌什县| 宁蒗| 铁岭市| 达尔| 库尔勒市| 台江县| 宜城市| 永嘉县| 邯郸市| 山丹县| 巫山县|