TLDR Tech / DevOps
How MVCC and Transactions Work in RocksDB
RocksDB builds MVCC around monotonically increasing sequence numbers, immutable key versions, snapshots, atomic write batches, and reference-counted views that prevent active readers from losing access to memtables or SST files. Its pessimistic and optimistic transaction modes differ mainly in when conflicts are detected, while snapshot isolation, write skew, phantom reads, and serializable behavior must be assembled from lower-level APIs such as snapshots, get_for_update, and range locks.
Read the full story