137: Tim Neutkens - Continuing to Innovate with Next.js 9.3

What It Covers

Tim Neutkens explains Next.js 9.3's paradigm shift from server-side rendering to hybrid static generation with get static props and get server side props, enabling per-page optimization without infrastructure lock-in to Vercel's platform.

Key Questions Answered

• •Static Props API: Get static props generates pages at build time with data fetching, eliminating server overhead for content that changes infrequently. Pages export async functions that fetch from any source—CMS, database, or filesystem—with code automatically tree-shaken from browser bundles.
• •Fallback Rendering: Get static paths with fallback mode pre-renders top pages at build time while generating remaining routes on-demand upon first request. Subsequent visits serve cached static HTML, avoiding full rebuilds for thousands of blog posts while maintaining instant performance.
• •Server Props Benefits: Get server side props always runs server-side, consolidating multiple API calls into one cacheable endpoint. This reduces round-trip latency for international users and enables direct database queries without exposing credentials to browsers, eliminating intermediate API layers entirely.
• •Incremental Regeneration: The revalidate key triggers background page regeneration after specified seconds, serving stale content instantly while updating for next visitor. Users never wait for renders—a one-second revalidate keeps content fresh without sacrificing speed, unlike traditional cache-busting approaches.
• •Portable Architecture: All Next.js features work on any Node.js host using next start command, not just Vercel. The framework uses standard HTTP request/response objects and stale-while-revalidate headers, allowing deployment to Heroku, AWS, or custom infrastructure with CDN configuration.