DDIA is a great book. It is a bad lab.

Description and use

DDIA offers theory but lacks practice. A lab with interactive diagrams, worked examples, and design exercises was created to bridge the gap and aid interview preparation.

Problem

Reading DDIA provides concepts but lacks a feedback loop, exercises, and failure scenarios, leaving readers unable to apply knowledge in interviews or real systems.

Outcome

The lab bridges the gap between theory and practice, providing interactive exercises that simulate failure scenarios like 2PC coordinator disappearance, enabling learners to reason under pressure and prepare for interviews.

Workflow

• Read DDIA chapters
• Identify gaps in practice
• Create interactive diagrams for key concepts
• Develop worked examples with initial state, operation, result, and reasoning
• Design 47 exercises with solutions and diagrams
• Publish lab on GitHub and Vercel
• Encourage community feedback and issue tracking

Evidence

DDIA is the best distributed systems book I have read. I finished the second edition with a head full of vocabulary and no way to check whether I actually understood any of it.

Source

What it does not have is a feedback loop. No exercises. No answer key. No failure timeline you can step through.

Source

So I built the lab I wanted while reading it.

Source

155 chapter diagrams. 89 are interactive step-throughs: write paths, failovers, quorums, 2PC, compaction.

Source

47 design exercises with full worked solutions, plus 118 diagrams inside those solutions.

Source