HOW MVCC AND TRANSACTIONS WORK IN ROCKSDB

Summary from the TLDR Data newsletter

RocksDB tags keys with increasing sequence numbers, so readers snapshot a consistent view while writers append without blocking. Pessimistic transactions lock on write - optimistic ones check conflicts at commit using pre-hashed mutexes. TiDB and CockroachDB skip native transactions and build their own layers.