nextjs№32
Next.js, zero to seniorNEXTJS
Rendering strategies, App Router, server components and caching layers — production Next.js.
- units
- 10
- lessons
- 32
- hours
- ~9
01
SSR, SSG, ISR, server components
Each rendering mode is a different answer to 'when does HTML get built and who pays the latency'.02
App Router, caching layers, server actions
App Router stacks four caches between you and fresh data; knowing which one bit you is the production skill.03
Route handlers, middleware, runtimes
Route handlers are your API surface; middleware runs on every matched request at the edge — and the runtime decides what code may exist.01Route handlers: route.ts as your HTTP surface — verbs, params, and the Next 15 caching flip17 min02Middleware and the edge of trust: matchers, rewrites, and CVE-2025-2992718 min03Node vs Edge runtime: cold starts, missing APIs, and why compute must live near data17 min04Streaming responses: ReadableStream, SSE for LLM UIs, and the proxies that buffer them18 min
04
Auth in the App Router
Auth in Next.js is a boundary question: middleware redirects, layouts don't protect, and every server action is a public endpoint.01Sessions vs JWT: revocation, rotation, and where the state lives on serverless17 min02Auth boundaries: why middleware and layouts cannot protect, and the Data Access Layer that can19 min03server-only and secrets: the module graph, NEXT_PUBLIC_, and what taint APIs actually catch18 min04CSRF and action security: every server action is a public POST endpoint18 min
05
Images, fonts, bundle budgets
Assets dominate LCP and INP: next/image and next/font exist to make the fast path the default — budgets keep it that way.06
Deployment and the edge
Self-host is a real option: standalone output in a container, edge for routing not data, ISR needs a shared cache behind more than one pod.07
Observability and errors
error.tsx is a boundary tree, not a page: instrumentation.ts wires OTel before anything runs, and RSC logs live on the server only.01error.tsx hierarchy: what each boundary actually catches, digests, and when reset() lies17 min02instrumentation.ts and tracing: one register() per process, one trace per request, and the sampling bill18 min03Server logging and Web Vitals: structured logs with request ids, and beacons that name the bad deploy17 min
08
Architecture at scale
Route groups are module boundaries: a monorepo splits by domain, shared code moves to packages, and pages→app migrates route by route.01Route groups as module boundaries: per-domain shells, colocation, and the full-reload tax17 min02Monorepo mechanics: pnpm workspaces, the Turborepo task graph, and packages that earn their boundary18 min03pages/ to app/ migration: coexistence, the translation map, and a quarters-not-sprints timeline18 min
09
The data layer
RSC talk to the database directly: pool per process not per request, serverless needs a proxy, cache tags model your domains.01ORM and SQL in server components: the data layer owns queries, memoization, and the tree-shaped N+118 min02Pooling on serverless: the multiplication problem, pgbouncer transaction mode, and per-lambda sizing17 min03Cache tags by domain: invalidation taxonomy, webhook wiring, and the over-invalidation storm16 min
10
Next.js in production
Production Next.js fails in cache poisoning, ISR storms and cold starts — this unit is incident anatomy plus the cost engineering math.Build with this track
Guided projects that exercise what you learn here.
Go, zero to senior
A small language for big systems — types, errors, interfaces, and concurrency that actually scales.