Choose a rendering strategy per route, not per app. Compare CSR, SSR, SSG, and ISR on TTFB, LCP, freshness, cost, and personalization.
Most teams pick a rendering strategy once ("we're an SPA", "we're on Next.js") and apply it everywhere. Architects treat it as a per-route decision driven by the route's constraints.
A product page, a logged-in dashboard, a marketing page, and a search results page have very different needs:
| Route | Data freshness | Personalized? | SEO-critical? | Traffic shape |
|---|---|---|---|---|
| Marketing / docs | Changes on deploy | No | Yes | Spiky, cacheable |
| Product detail | Minutes–hours | Partly (price, stock) | Yes | Long tail |
| Search results | Per request | Partly | Somewhat | High cardinality |
| Dashboard | Real time | Fully | No | Authenticated |
The four classic strategies:
None of these is "best". Each one moves cost and latency to a different place: the user's device, your servers, or your build pipeline.