Hidden amplification
One page request can quietly fan out into dozens of database reads. The client sees one request; the database sees the real cost.
Interactive Systems Explainers
N+1 Query Playground
See how one calm page request can explode into hidden database work, and how batching keeps the flow under control.
Related Concepts
Key Observations
What to Notice
N+1 example
A store loads products, then seller, inventory, and reviews for each product. With 100 products, that page can become hundreds of reads.
Batched loading example
The app loads all sellers together, all inventory together, and all reviews together. A few larger reads replace a swarm of tiny ones.
Why latency climbs
When the pool is full, new queries wait. More items or a small traffic bump can push the same page into a much slower shape.
Interactive Systems Explainers