Apr 5 · 29 min read · TLDR: 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 di
Join discussion
Mar 29 · 7 min read · Scaling PostgreSQL to 800 Million Users: OpenAI's Surprisingly Simple Secret Spoiler alert: It's just one primary database and 50 read replicas. That's it. When you hear that OpenAI serves over 800 mi
Join discussion
Mar 16 · 9 min read · Sharding splits one massive database into smaller independent ones. Uber built Schemaless in 2014 — 4096 shards on top of MySQL — to survive explosive growth. Here's everything you need to know as a b
Join discussion
Mar 12 · 13 min read · TLDR: Sharding means splitting one logical dataset across multiple physical databases so no single node carries all the data and traffic. The hard part is not adding more nodes. The hard part is choos
Join discussionFeb 25 · 7 min read · In the previous two articles, we saw something important: To scale reads, we reduce the work the database does per query. [LINK] To scale writes, we reduce the work the database does per insert. [LINK] But what happens when a system has both heavy ...
Join discussionFeb 12 · 11 min read · Why Traditional Scaling Approaches Fail at Modern Scale Vertical scaling—adding more CPU, RAM, and faster storage to a single database server—hits hard limits around 96-128 cores and a few terabytes of RAM. Cloud providers offer increasingly powerful...
Join discussionFeb 12 · 7 min read · Database Sharding: Horizontal Partitioning Strategies Understanding Database Sharding in Modern Distributed Systems As applications scale beyond single-server capabilities, database sharding emerges as a critical horizontal partitioning strategy. Whi...
Join discussion
