“Scale” is one of the most over-used words in product

Founders worry a lot about scale. Will the architecture hold up at a thousand users? Ten thousand? A million? Should we use that database, that hosting setup, that pattern, because it scales?

Most of these conversations happen prematurely. They’re scaling concerns being raised before scale is actually a problem — and the worry pulls effort away from the more pressing question of whether anyone wants the product at all.

Not everything needs to scale. Some parts of your system need to handle volume gracefully. Others can stay manual, slow, or fragile, and the product is fine. Knowing the difference is part of avoiding premature optimisation.

What “needs to scale” really means

Something needs to scale when it has to keep working well as us...

What actually needs to scale (and what doesn’t)