Next.js 16.4 · App Router · Cache Components
See how Next.js really moves data between browser and server.
Three hands-on tutorials on an interactive architecture map. Real Server Actions, real caches, real cookies. Every step on screen says whether it was measured, inferred or simulated.
scroll · three tutorials belowThree tutorials, one map
Server Actions & revalidation
Add a product through a real Server Action. Choose what it calls afterwards and watch whether the list updates, stays stale, or re-renders from cache.
'use server' · 'use cache' · updateTag · revalidateTag
OpenCookies vs localStorage
Two live theme switchers. One flashes on reload and one does not. The frame measures the gap itself, and the map shows why the server could only read one of them.
cookies() · first paint · hydration
OpenServer vs Client Components
Drop components into a page, decide where 'use client' goes, and watch what crosses into the browser bundle and what stays on the server.
'use client' · children · bundle
OpenNothing is hand-waved
A diagram that never runs can show anything. Here the tutorials run the real runtime, and every step is labelled with where it came from.
- measured
- Timestamped by this app on the server or in the browser. A real event.
- inferred
- Deduced from something observable changing, such as a Server Component prop after an action.
- simulation
- A scripted step for teaching. No real request happened for this event.