How do SSR, SSG, and ISR differ in production tradeoffs?
PICTURE THIS: DATA SPLIT
Fit on train, tune on val, report on test once.
Simple meaning
SSR is always fresh and more expensive per request, good for user-specific HTML.
WHY — Next.js instead of guessing?
Why interviewers care about Next.js:
question about Next.js.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1SSR is always fresh
and more expensive per request, good for user-specific HTML.
- 2SSG is cheapest and
fastest at the CDN but stale until rebuild.
- 3ISR revalidates in the
background so marketing pages stay fast without a full rebuild.
- 4I pick based on
personalization and freshness, not fashion.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
SSR is always fresh and more expensive per request, good for user-specific HTML. SSG is cheapest and fastest at the CDN but stale until rebuild.