Skip to content

ElMoorish/system-design-bible

Repository files navigation

system-design-bible

System design for the AI era. The Primer updated, extended, and maintained.

Stars Contributors Last Commit License PRs Welcome

Why this repo

  • Beyond the Primer: We add the AI infrastructure patterns that reached production after 2022.
  • Original Synthesis: We write original explanations and diagrams instead of just aggregating links.
  • Reference Manual: This is a free, open-source reference manual designed to be maintained indefinitely.

Who this is for

This repository is for software engineers with 2+ years of experience who are preparing for system design interviews at L4–Staff level or building production systems using LLMs, agents, and vector databases. Not for: Total beginners, ML researchers, or those seeking code tutorials.

Structure Overview

flowchart LR
  F[Foundations] --> A[AI Era]
  A --> M[Modern Patterns]
  M --> C[Case Studies]
  C --> I[Interview Guide]
Loading

Table of Contents

Foundations

AI Era

Modern Patterns

Resources

What is new vs the Primer

Topic System Design Primer System Design Bible
Latency Metrics Uses 2012 Jeff Dean numbers Uses 2026 NVMe and GPU HNSW numbers
LLM Serving No coverage vLLM, continuous batching, KV cache
RAG No coverage semantic chunking, hybrid search, reranking
AI Agents No coverage multi-agent sync, tool-calling reliability, MCP
Databases SQL vs NoSQL split NewSQL, Vector DBs, and sharding logic
Hardware Magnetic disk focus NVMe and H100 GPU memory focus
Streaming Basic Kafka Flink watermarks, SSE for LLM tokens
Edge CDN static caching Wasm isolates, edge inference, stateful edge
Transactions 2PC and distributed locks Saga patterns and transactional outbox

Note

⭐ Star this repo to follow monthly updates as the field evolves. New patterns, case studies, and interview questions added every month.

Contributing

Contributions are what make the open-source community an amazing place to learn, inspire, and create.

  1. Add a production resource to an existing chapter.
  2. Propose a new case study from a recent engineering blog.
  3. Fix an outdated benchmark with a verified source. See CONTRIBUTING.md for details.

Releases

No releases published

Packages

 
 
 

Contributors