Next.js

Server components, hydration, rendering and caching

The Next.js Caching Model

Four different caches, four different lifetimes — why 'my data won't update' in the App Router almost always comes down to not knowing which one is holding the stale value.

Next.jsCaching

9 min read

Server Actions & Data Fetching in Next.js

How Next.js collapses the client-server round trip for mutations and reads alike — and the cases where you still want a real API route.

Next.jsServer Actions

8 min read

Streaming & Suspense in the Next.js App Router

Why one slow data fetch shouldn't block an entire page — and how Suspense boundaries let the App Router send HTML in pieces as they become ready.

Next.jsStreaming

8 min read

SSR vs. SSG vs. ISR: Choosing a Rendering Strategy

Three ways to turn a page into HTML — and the two questions that actually decide which one you need.

Next.jsSSR

9 min read

Hydration: What It Is and Why It Breaks

The server sends HTML that already looks right — hydration is the step where React quietly takes it over, and the step where mismatched renders turn into console warnings.

Next.jsHydration

8 min read

★ Featured

React Server Components vs. Client Components

Server Components ship zero JS by default and Client Components buy interactivity at a cost — the App Router forces you to choose deliberately, per component.

Next.jsReact Server Components

9 min read