Core concepts
The building blocks. Explained clearly.

Core Mechanics: Relational databases sit atop volatile RAM (buffer pools) and block-oriented disks that can fail mid-write while hundreds of clients mutate overlapping rows concurrently.
Visual & Structural Flow: Depicts WAL + MVCC Commit & Crash-Recovery Architecture (SQL Client (txid=8421) -> Buffer Pool + MVCC -> pg_wal (Sequential) -> pg_xact + Heap Pages); Write Skew Under Snapshot Isolation vs. Serializable Detection (Tx 1 (Dr. Alice) -> MVCC Snapshot -> Tx 2 (Dr. Bob)); ACID Transaction & Retry State Machine (ACTIVE -> COMMITTED -> ABORTED (40001)).
Trade-Offs & Production: Choosing an isolation level or coordination model trades throughput against anomaly prevention. High-throughput payment and order systems combine NVMe-backed WAL group commit (commit_delay batching multiple concurrent COMMITs into a single fsync) with the Transactional Outbox pattern.
Failure Modes & Application: Explore how ACID internals—MVCC snapshots, gap locks, XID wraparound, and transactional outboxes—manifest in real production incidents and system designs.
A handbook for software systems
Complex systems. Clear thinking.
Learn how engineering systems work, where they fail, and how to make sound design decisions.

Find your starting point
The building blocks. Explained clearly.
Real requirements. Concrete designs.
Patterns in the context that matters.
How to structure, reason, and prepare.
ACID guarantees that database transactions execute as all-or-nothing units (Atomicity), preserve schema and domain invariants (Consistency), shield concurrent readers/writers from partial state (Isolation), and survive power loss once acknowledged (Durability) via write-ahead logging (WAL), fsync, and concurrency control (MVCC/2PL).
Learn by doing
Connect services, data, and scale.
Turn requirements into clean abstractions.
Make the logic work, then make it efficient.