Development9 min readMay 02, 2026

Next.js in production: decisions that don't cost you in 18 months.

Code written fast today is code rewritten expensively in 18 months. Architecture is the only debt that charges interest.

Antto Cattalano
Antto Cattalano
Co-Founder · Diseño Gráfico & UX/UI
Next.js in production: decisions that don't cost you in 18 months.

Decisions that matter on day one

Server Components by default, Client Components only where real interactivity is needed. That single rule avoids half the performance problems we see in projects migrated from Create React App.

Typed data from the source, not inferred halfway through. If the data shape changes on the backend, we want the build to fail — not the user to see a blank screen in production.

The right architecture doesn't show in month one. It shows in month 18, when everything else keeps growing without breaking.

What we avoid on purpose

Dependencies that solve a problem we don't have, early abstractions for a scale that hasn't arrived yet, and global state where props are enough. Every layer that isn't justified today is a layer someone will have to understand tomorrow.