جلب البيانات في RSC

Welcome to data fetching in Next.js Server Components! Traditionally, data fetching often happened on the client-side, leading to heavier JavaScript bundles.

Server Components (RSCs) change this by allowing you to fetch data directly on the server, before any JavaScript is sent to the browser.

In a Server Component, you can use standard JavaScript async/await syntax with the native fetch API to get data.

• No need for client-side hooks like useEffect.
• Data fetching runs entirely on the server.
• The fetched data is rendered into HTML.

Imagine fetching a list of products or user profiles. In a Next.js Server Component, your component function can be marked as async, allowing you to await the result of a fetch call.

This means your component receives the data before it's even sent to the browser for rendering.

Here's a simplified Node.js example demonstrating how fetch works with async/await, similar to how it would operate within a Next.js Server Component.

Run it to see how data is retrieved from an external API.

When you await a fetch call in an RSC, the server pauses rendering that part of the component until the data arrives. Once the data is ready, the component continues rendering.

This ensures the initial HTML sent to the client already contains all the necessary data, improving perceived load times.

One major advantage of fetching data in Server Components is that server-only logic, like database queries or API keys, never leaves the server.

This significantly enhances security, as sensitive information is not exposed to the client's browser.

By fetching data on the server, the client doesn't need to download extra JavaScript bundles for data fetching libraries or complex data hydration logic.

This results in:

• Faster initial page loads.
• Less JavaScript for the browser to parse and execute.
• Improved performance, especially on slower networks.

Server Components can fetch data from various sources:

• External APIs: Using fetch for REST or GraphQL endpoints.
• Databases: Directly querying a database (e.g., with Prisma client).
• File System: Reading local files (e.g., Markdown content).

The key is that these operations happen on the server.

In this lesson, we explored how to fetch data efficiently using Next.js Server Components.

• RSCs use async/await and fetch to get data on the server.
• This keeps sensitive logic server-side and reduces client-side JavaScript.
• The result is faster initial page loads and improved security.

Next, we'll look at interactivity with Client Components!