Documentation Course
System Design In-Depth
From the Silicon to the Multi-Region Ledger
A complete system design curriculum that starts at the memory hierarchy and ends at a multi-region ledger — 64 modules for engineers who have to build the thing, not just whiteboard it. Foundation covers the machine, the estimation math, and one server done properly. Practitioner covers distributed data, storage engines, sharding, Kafka, caching, and search. Architect covers consensus, sagas, multi-region topology, and the failure modes of distribution itself. Production & Governance covers observability, zero-downtime migrations, chaos engineering, disaster recovery, FinOps, and compliance. Every trade-off is stated as a trade-off with its cost named, and every internal is anchored to the production symptom that makes you care.
How to use this course
This course works as both a sequential read and a standalone reference. Read front-to-back to build the model from the memory hierarchy up to a multi-region ledger — each phase assumes the one before it. Or jump to the module that matches the decision in front of you: an estimation you have to defend, a sharding key you can't take back, a rebalance storm, a migration on a multi-terabyte table, or a cloud bill nobody can explain.
Total reading time
~27 hrs
across 64 live modules
Built from
UPI-scale payments
Postgres, Redis, Kafka, multi-region
Prerequisite
You ship backend systems
Beginner through architect — no distributed systems background assumed

Your instructor
Jatin Jain Saraf
Architect of SupraScan, Supra Blockchain's explorer and indexer: 500–1,000 TPS on a PostgreSQL database that grew to 10 TB, now 2.7 TB. The case studies show the production work behind these courses.
See it in production
- Case studyIndexing a Blockchain in Real Time, at ScaleA blockchain never pauses for maintenance. Here's how SupraScan's indexer stays caught up, decomposes every transaction into a dozen relational tables, and survives its own concurrency bugs without losing data.
- Case studyFrom a Redis Relay to a Direct Feed: Rebuilding the Real-Time PipelineThe old real-time pipeline worked. It also had a hop nobody needed anymore. Ripping it out across five repos took verified-dead traffic checks, a careful merge order, and knowing exactly which lookalike code path to leave alone.
- Case studyWhat It Would Take to Hit 500K TX/Sec, and Why That's the Honest AnswerEvery scaling lever on the table, measured honestly, still lands 25x short of a 500,000 tx/sec target. Here's the capacity-planning math, and why the right answer was to say so instead of overselling a smaller win.
- Case studyBecoming the Readiness Gate for Another Team's Scale-UpOne team validated their system could handle 100,000 concurrent tasks. They still wouldn't turn the dial on a live network until a different team's indexer proved it was ready. That's a real dependency, not a hypothetical one.
- Case studyA Type Migration Across Three Services: VARCHAR to BIGINT at ScaleThe migration itself was the easy part. The real risk was every downstream function quietly assuming a column would always come back as a string. Two hotfixes later, that assumption was gone.
- Case studyA Reliability-Hardening Sprint: Isolation, Guardrails, and a Query Plan That Went From 45 Million to 206None of these fixes were triggered by an outage. Per-network cache isolation, timeouts on every resolver, dead-code removal, a partition-pruning fix with a genuinely startling before/after number, and a real external security report handled the right way.
Phase 1 — Foundation
Absolute basics · No prior knowledge assumed
Phase 2 — Practitioner
Production patterns · Real application architecture
Phase 3 — Architect
Engine internals · High-throughput systems · Distributed architecture
Phase 4 — Production & Governance
Running it, funding it, proving it · Observability, migrations, DR, FinOps, compliance