Whetstone

Next.js & the Network

What crosses the wire in a Next.js 16 app, and who decides. Where each piece of code runs — Server Components, Server Actions, Route Handlers — and what that means for auth; the HTTP caching and compression headers every response carries, and which layer wins when two set them; Next's own Cache Components model (use cache, cacheLife, cacheTag, updateTag) and what changed from Next 14/15; and streaming with Suspense, where the status code is fixed at the first byte. Each unit closes on the production traps that pass every local check.

  1. 1. Server Components, Server Actions & Route Handlers: where code runs

    Full · Core · ~40 min
    • Auth
    • Next.js
    • Server Components
    • Server Actions
    • +1 moreAdditional skills: Route Handlers

  2. 2. Response headers: HTTP caching & compression

    Full · Core · ~45 min
    • HTTP
    • Caching
    • Next.js
    • Cache-Control & HTTP Caching
    • +1 moreAdditional skills: Compression

  3. 3. Next.js caching & revalidation: Cache Components

    Lesson · Advanced · ~45 min
    • Caching
    • Next.js
    • Cache Components
    • Revalidation

  4. 4. Streaming & Suspense: the response as a stream

    Lesson · Advanced · ~40 min
    • HTTP
    • Next.js
    • Streaming
    • Suspense