ทำความเข้าใจ RSC และ RCC

In Next.js 15, building user interfaces relies heavily on React components. But there's a new twist!

• Traditionally, all React components run in the user's browser.
• Next.js 15 introduces two main types: Server Components (RSC) and Client Components (RCC).
• Understanding their differences is crucial for building fast, efficient, and interactive Next.js applications. Let's dive in!

React Server Components (RSC) are components that run exclusively on the server, before any JavaScript is sent to the browser.

• They generate HTML directly on the server.
• This HTML is then sent to the client, along with any necessary client-side JavaScript for interactive parts.
• RSCs are the default component type in the Next.js App Router.

Here's a basic component. Since there's no 'use client' directive and no interactive features (like state or event handlers), Next.js treats this as a Server Component by default.

It runs on the server, renders its HTML, and that's what the browser receives.

RSCs offer significant advantages for performance and efficiency:

• Zero Client JS: They don't add to the client-side JavaScript bundle, leading to faster page loads.
• Direct Server Access: Can directly access server resources (like databases or file systems) without needing client-side API calls.
• Improved SEO: Content is rendered on the server, making it easily crawlable by search engines.
• Enhanced Security: Sensitive logic and data fetching stay on the server.

React Client Components (RCC) are what you're likely familiar with – they run entirely in the user's browser, just like traditional React components.

• They enable interactivity, client-side state management, and access to browser-specific APIs (like localStorage or navigator).
• RCCs require JavaScript to be downloaded and executed in the browser.

This component uses useState to manage a counter and an event handler to update it. Because it needs client-side interactivity, we mark it with 'use client'.

This directive tells Next.js to send this component's JavaScript to the browser for execution.

The 'use client' directive is a critical marker in Next.js:

• It must be placed at the very top of a file, before any imports.
• It signals to Next.js that this file, and any modules it imports, should be treated as part of the client bundle.
• This directive acts as a 'boundary' – everything below it, including imported child components (unless explicitly marked as RSCs), will render on the client.

Here's a quick comparison of RSCs and RCCs:

• Execution: RSC (Server), RCC (Browser)
• Interactivity: RSC (No), RCC (Yes, with hooks/events)
• State/Effects: RSC (No), RCC (Yes, useState, useEffect)
• Bundle Size: RSC (Adds zero client JS), RCC (Adds to client JS bundle)
• Data Access: RSC (Direct server resources), RCC (Needs client-side fetching or props)
• Directive: RSC (Default, no directive), RCC (Requires 'use client')

Choosing between RSC and RCC depends on your component's needs:

• Use RSC for: Static content, initial data fetching (e.g., from a database), SEO-critical parts, components that don't need client-side interactivity.
• Use RCC for: Interactive UI elements (buttons, forms), client-side state management, components requiring browser APIs (e.g., geolocation, local storage), animations.

Often, you'll compose RSCs and RCCs together for a powerful user experience!

You've learned the core differences between Server and Client Components in Next.js 15!

• Server Components (RSC): Run on the server, generate HTML, reduce client JS, are the default.
• Client Components (RCC): Run in the browser, enable interactivity and state, require the 'use client' directive.
• Combining them allows you to build highly performant and dynamic web applications.

Next, we'll explore how to fetch data specifically within Server Components efficiently!