Topic
Scalability
Learn Scalability as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts19 Articles5h 16m
Overview
Learn Scalability as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
System Design
Distributed Systems
Architecture
Hld
Learning Path in this Topic
Series that contain articles from Scalability. Select a path to filter the article list.
Articles
19 matched articles
Article 1Partitioning Approaches in SQL and NoSQL: Horizontal, Vertical, Range, Hash, and List PartitioningTLDR: Partitioning splits one logical table into smaller physical pieces. The database skips irrelevant pieces entirely — turning a 30-second full-table scan into a sub-second single-partition read. S12 min
Article 2Sharding Approaches in SQL and NoSQL: Range, Hash, and Directory-Based Strategies ComparedTLDR: Sharding splits your database across multiple physical nodes so no single machine carries all the data or absorbs all the writes. The strategy you choose — range, hash, consistent hashing, or di29 min
Article 3ID Generation Strategies in System Design: Base62, UUID, Snowflake, and BeyondTLDR: Short shareable IDs need Base62 (URL shorteners). Database primary keys at scale need time-ordered IDs (Snowflake, UUID v7). Security tokens need random IDs (UUID v4, NanoID). Picking the wrong 26 min
Article 4Write-Time vs Read-Time Fan-Out: How Social Feeds ScaleTLDR: Fan-out is the act of distributing one post to many followers' feeds. Write-time fan-out (push) pre-computes feeds at post time — fast reads but catastrophic write amplification for celebrities.18 minArticle 5System Design HLD Example: Hotel Booking System (Airbnb)TLDR: A robust hotel booking system must guarantee atomicity in inventory subtraction. The core trade-off is Consistency vs. Availability: we prioritize strong consistency for the booking path (Postgr15 minArticle 6System Design HLD Example: E-Commerce Platform (Amazon)TLDR: A large-scale e-commerce platform separates catalog, cart, inventory, orders, and payments into independent microservices. The core architectural challenge is Inventory Correctness during flash 13 minPage 1 of 4