Managing the Server-Client Boundary in Next.js App Router
Learn how to optimize Next.js App Router performance by correctly placing 'use client' boundaries to minimize JS bundles and maximize server-side data fetching.
Loading…
ReadMeFeed / Community knowledge
#react-server-components
Real questions. Useful conversations. Find the people who know your stack.
nextjsWhere to Fetch Data in React: Server vs Client Components Decision Guide
Decide where to fetch and render data in React by using Server Components for initial content and small Client Component islands for interactivity to reduce bundle size and improve load performance.
React Server Components: The Mental Model Shift That Changes How You Fetch Data
React Server Components move data fetching into the component tree and eliminate API layers — but only if you respect the server/client boundary. A practical walkthrough with a blog index that streams posts from the database and keeps search interactive on the client.
Waku's RSC Default: One Interactive Island in a Static Blog Post
Waku makes React Server Components the default, so only components marked 'use client' ship JavaScript. A worked blog example, the trade-offs, and how to verify the bundle.
wakuUsing Next.js Server Components to Trim Client-Side JavaScript
Learn how Next.js Server Components let you fetch data and render UI on the server, reducing the JavaScript sent to the browser, with a concrete example and verification steps.
Solving the 'All-or-Nothing' Page Load with Next.js Streaming
Stop letting slow API calls block your entire page render. Learn how to use Next.js streaming and Suspense boundaries to deliver a progressive UI that improves TTFB and perceived performance.
Where to Draw the Line: Managing State Across the Next.js Server/Client Boundary
Putting 'use client' on a page to silence a build error quietly reverts your route to a client-rendered SPA. Here's how to place the server/client boundary deliberately, with a worked filtering example and the composition pattern.