In Parts 1-3, we built a storage engine: WAL, memtable, SSTables, and compaction. Every operation is...
In Parts 1-3, we built a storage engine: WAL, memtable, SSTables, and compaction. Every operation is a single GET or PUT.
But real applications rarely need just one write at a time.
Problem: Multiple Writes Need to Be Atomic
Consider a bank transfer: move $100 from account A to account B.
PUT account_A 400 (was 500, debit 100)
SaarDB is a learning project: build a relational database from first principles in Go, one layer at a...
In Blog 5, we built a SQL parser. It can take this: INSERT INTO payments VALUES (500, payment_1,...
A transaction groups several database writes into one atomic unit. Either all of them commit, or none...
A systems architectural analysis of Write-Ahead Logs, Sorted String Tables, Bloom filters, and LSM-tree compaction strategies.
In Parts 1-4, we built a transactional key-value store. It has WAL for durability, memtables and...
In part 1, the single-document case was easy. In part 2, two documents brought Write Skew, and we saw...
