Sharding
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
When a database becomes too large for a single machine to handle, it is horizontally split into multiple independent shards, each storing a portion of the data and distributed across different servers.
SCAFFOLDING EFFECT
Reduce cognitive load
- Infinite scalability: As a company grows, don't try to have one CEO manage everything (single-machine bottleneck). "Shard" the company into multiple independent business units (Amoeba/divisions), each responsible for its own profit and loss, achieving horizontal scaling.
Anchor fast decisions
Horizontal sharding distributes data rows to different physical nodes based on a shard key (e.g., modulo of user ID), with each node responsible for a subset. The mechanism is "divide and conquer + shared-nothing"—a single node failure or capacity limit does not affect the whole, and scaling is achieved by adding nodes (horizontal scaling).
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Shard_%28database_architecture%29verified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS