0
Challenge · 46Interview Gauntlet

RSC vs CSR vs SSR + hydration

Modelused in ~92% of apps

Three letters — RSC, SSR, CSR — get conflated in almost every interview, and the person who can draw the actual timeline (server HTML → stream → hydrate) and say exactly when a hydration mismatch fires is the one who gets the offer. This is the concept that separates 'I used Next.js' from 'I understand Next.js.'

Core idea. RSC (React Server Components) render to a serialized payload and ship zero JS; SSR turns Client Components into HTML on the server for a fast first paint; CSR is the browser rendering from JavaScript. Hydration is the step where the client re-runs your Client Components and attaches event handlers to the already-painted server HTML — and it fails loudly when the server HTML does not match the first client render.
Playground, this isn't a screenshot
0
Idle
1
Server render
2
Stream chunks
3
First paint
4
JS arrives
5
Hydrated

Request the page

browser viewportblank
waiting for request…
server: renderToPipeableStream(<App/>)
stream: <html>… flushed in chunks →
stream: <Suspense> fallback first, then data
browser: paint HTML (fast FCP, no JS)
browser: download client bundle.js
hydrateRoot(el, <App/>) — attach handlers
JS attached: no
Try clicking Like before stage 5.
↑ play a little first, then dig in