Scalability
Handling growth in load (users, requests, data) without degrading — vertical vs horizontal scaling.
Why we need this / what value this brings
Scaling problems are far cheaper to fix before they're urgent than mid-incident under real load.
When to use this
Once there's a concrete growth signal (traffic trend, a specific slow endpoint) — not speculatively.
How to use or implement this
Profile the actual bottleneck first (usually the DB) before reaching for horizontal scaling or infra changes.
Research questions
- What's Localz's first actual scaling bottleneck likely to be (DB connections? a single hot table?)?
Empty folder — drop notes, links, and findings here as you research.