Blog

Parallel routes let a single layout render multiple independent pages at once. Combine them with intercepting routes and you get URL-aware modals with zero hacks.

Server Actions collapse form handling into a single server function—no API route, no manual fetch, no useState for loading. Here's the pattern that replaces 80% of your mutation boilerplate.

Four caching layers, three revalidation APIs, and the Next.js 16 rename that turns everything you learned in 15 into the "previous model". Here's the complete mental model for data fetching in the App Router.

One call with the wrong argument type, made once, makes the next 100 million integer additions roughly 3x slower. Hidden classes, inline caches, the tier-up thresholds and every deopt reason — checked against what Node 22 actually does, not what the blog posts say.

Most Node.js services drop in-flight requests on every deploy. Here's the complete pattern: SIGTERM handling, HTTP draining, queue cleanup, and Kubernetes integration.

If you're still writing pages/api/... files in a new Next.js project, stop. Route Handlers are the App Router's replacement, and they're meaningfully better — typed, streaming-capable, and built on the same Web platform APIs that Cloudflare.

Your user-facing API is fine. REST, JSON, OpenAPI docs — it works, everyone can call it, no complaints. But internally, your Order service is calling the Inventory service 40 times per request.

You've probably seen gRPC described as "REST but faster." That framing is technically true and practically useless.

Node.js has two module systems that don't interoperate cleanly. Here's how CommonJS and ESM work, how Node resolves imports, and how circular dependencies behave in each.