snapshot-isolation

Transactional schema-less embedded database used by JetBrains YouTrack and JetBrains Hub.

Nornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Using Neo4j Bolt/Cypher and qdrant's gRPC means you can switch with no changes while adding intelligent features like schemas, managed embeddings, reranking+llm, GPU accel, Auto-TLP, Policy-based Memory Decay, and MCP server.

A microsecond-latency ACID database engine with a native Entity-Component-System data model, built for real-time systems.

Standalone, deterministic MVCC engine for building transactional key-value databases in Rust — timestamp-ordered versions, two-phase intent transactions, guarded writes, and incremental GC. The open-source core of the Nexir database.

Tesseract: Efficient Online Schema Evolution for Snapshot Databases (VLDB 2023)

仓库 with an implementation of MVCC and serialized snapshot isolation in an in-memory KV store.

Class assignments for the course Advanced Database Systems (CS60113) [IIT Kgp]

MVCC transaction primitive for Rust databases - snapshot isolation, SSI, deadlock detection.

An embeddable MVCC key-value store for time-travel queries, offering snapshot isolation, lock-free single-writer/multi-reader concurrency and incremental compaction.

a toy database support snapshot isolation

Implementation of a data storage subsystem on disk (buffer pool) and transaction service at the snapshot isolation level.

DAFSA-backed Datalog engine in C: load facts, compile Datalog to a VM, materialize + serve from mmap snapshots. Docs: https://fixpointlinux.org/datalog-dafsa/

Multi-version concurrency control store as a pure value in Standard ML: snapshot isolation, first-committer-wins, GC. MLton + Poly/ML.

Go-based gRPC metadata control plane for table catalogs, snapshots, partitions, and transactions

LSM-tree key-value storage engine in Rust, from scratch with no storage deps. lattice-core crate + mdBook documenting every design decision. Snapshot transactions with conflict detection, async via tokio.

Google’s Percolator distributed transaction protocol 🌐🤝

Versioned key→record store over a content-addressed blob store: atomic commits, snapshots, lock-free three-way merge

See isolation levels break, step by step: run two transactions on a real MVCC engine and watch dirty reads, phantom reads, and write skew happen.

Transaction isolation, implemented and convicted: an MVCC engine with four isolation levels including Cahill's SSI, and a dependency-graph checker that finds G0, G1a, G1b, G1c, G-single and G2-item in observed histories