Track · Intermediate
Next.js in Production
Most Next.js confusion is really confusion about where code runs and what gets cached. This track walks the whole request path — component boundaries, the cache layers, mutations, and the parts that only hurt after deploy.
Before you startWhat you should already know
- Comfortable with React and hooks
- Have built at least one Next.js app
Curriculum4 lessons, in order
- 9 min
Where your code actually runs
Server and client components are not a performance setting. They are a boundary in your program, and the boundary has rules.
- 11 min
The four caches, and which one is lying to you
Next.js has several independent cache layers. Almost every "why is my data stale" bug is one specific layer, and naming it makes the fix obvious.
- 10 min
Mutations without an API layer
Server actions remove a whole tier of boilerplate. They also remove the tier where you were doing your validation, so put it back.
- 8 min
The parts that only hurt after deploy
Environment variables, error boundaries, streaming, and the handful of things that behave differently the moment real traffic arrives.