Skip to content

System Design Overview

First PublishedLast UpdatedByAtif Alam

This section gives a spine for architecture and design reviews: questions to ask stakeholders, checklist-style patterns, and links into deeper guides elsewhere in the library (databases, networking, observability, CI/CD, security). It complements operations-focused pages rather than replacing them.

Use the condensed page first — design review checklist — when you want a single pass before a review or RFC.

  1. Requirements and SLAs
  2. Capacity estimation
  3. Data modeling and storage
  4. API design (implementation depth: HTTP, payloads, layouts)
  5. Read scaling
  6. Write scaling
  7. Caching patterns
  8. Consistency and transactions
  9. Fault tolerance
  10. Observability for systems
  11. Security, deployment, and tradeoffs

Reference: Abbreviation glossary.

TopicWhat It Covers
Design review checklistOne-page bullets and sequencing for fast review
Requirements and SLAsRead/write mix, scale targets, SLAs, consistency and geography
Capacity estimationQPS, storage, bandwidth, bottlenecks
Data modeling and storageSQL vs NoSQL, normalization, indexes, sharding
API designREST, gRPC, GraphQL, errors, pagination, idempotency; HTTP contracts and layouts for implementation
Read scalingCache, replicas, CDN, fan-out, materialized views
Write scalingQueues, batching, async paths, pooling, sharding
Caching patternsAside, write-through, eviction, stampedes
Consistency and transactionsStrong vs eventual, sagas, CAP and PACELC
Fault toleranceRetries, breakers, degradation, release safety
Observability for systemsLogs, metrics, traces, RED/USE, postmortems
Security, deployment, and tradeoffsTrust boundaries, rollout patterns, documenting decisions
GlossaryCommon abbreviations
NeedWhere to Go
Database operations and on-callDatabases
HTTP and edge behaviorNetworking
Deep observability stackObservability
Deployment and pipelinesCI/CD
Security and complianceSecurity
Incidents and readinessQA
Process and communicationPractices