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

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.

主站蜘蛛池模板: 民丰县| 曲松县| 延寿县| 册亨县| 内丘县| 马公市| 黎城县| 石家庄市| 文安县| 丰台区| 务川| 读书| 新绛县| 康乐县| 中方县| 芦溪县| 金山区| 宁乡县| 宿迁市| 平远县| 高碑店市| 金乡县| 治多县| 德保县| 育儿| 遂溪县| 三台县| 闸北区| 抚松县| 石台县| 九龙县| 阜新| 阿鲁科尔沁旗| 察雅县| 英德市| 吉林市| 辽阳市| 嘉善县| 阿鲁科尔沁旗| 达州市| 兴业县|