Engineer Atlas
OverviewLearnInternalsModeling LabPlaygroundDatabase FinderRoadmapPracticeInterview
OverviewLearnInternalsModeling LabPlaygroundDatabase FinderRoadmapPracticeInterviewCheat SheetCompare
Database Engineering
  • Database Fundamentals
  • SQL
  • Relational Modeling
  • Normalization & Denormalization
  • Indexes
  • Query Execution & Optimization
  • Transactions
  • Concurrency & Isolation
  • PostgreSQL
  • Redis
  • NoSQL & Data Models
  • Vector Databases & Retrieval
  • Scaling
  • Distributed Databases
  • Caching
Database Internals
  • Overview
  • Build AtlasDB
  • Storage, Records & Pages
  • Index Internals
  • Buffer Management
  • WAL & Recovery
  • Transactions & MVCC Internals
  • LSM Trees
  • Query Engine
  • PostgreSQL & InnoDB Internals
  • Distributed Internals
  • Performance Internals
Database/Learn/Scaling
Database Engineering

Scaling

One user to millions: connection pooling, read replicas, caching, partitioning, sharding — in that order.

See how this works internally:Distributed Internals →Performance Internals →
Scaling from One User to Millions
▶ interactive

Scale in the cheapest order — indexes, connection pool, read replicas, cache, partitioning, sharding — because each step buys capacity by adding a problem, and skipping to sharding is adding the biggest problem first.

Engineer Atlas
GitHub·LinkedIn