การดึงข้อมูลฝั่งเซิร์ฟเวอร์

Next.js 15 excels at rendering your application on the server. This is super powerful for performance and SEO!

When you fetch data directly on the server, your users see content faster because the HTML is already built with data. It also helps search engines index your content better.

• Performance: Faster initial page loads.
• SEO: Content is available for crawlers.
• Security: Keep sensitive logic on the server.

In Next.js 15 Server Components, the standard fetch Web API is automatically enhanced. This means it comes with built-in caching and revalidation features.

You can use fetch directly inside your async Server Components to get data from external APIs or your own backend services.

Let's see how simple it is to fetch data. Here, we'll get a single "Todo" item from a public API. Notice the async keyword on the component function.

Next.js handles the waiting for data before rendering the component.

This JavaScript code demonstrates fetching data from a public API. While a Next.js Server Component uses JSX, the underlying fetch logic is the same. Run it to see the data!

By default, Next.js automatically caches the results of fetch requests in Server Components. If the same fetch request is made again (e.g., across multiple components or re-renders), Next.js will use the cached data.

This is fantastic for performance as it avoids redundant network requests.

Sometimes, you need the freshest data, bypassing the cache. You can do this by passing an option to fetch: { cache: 'no-store' }. This tells Next.js to always refetch the data.

Use 'no-store' for highly dynamic data that changes frequently and needs to be up-to-date on every request.

What if you want cached data, but also want to specify how often it should be considered "fresh"? You can use the next.revalidate option with fetch.

This sets a time-to-live (TTL) for the data. After this time, the next request will refetch the data and update the cache.

Choosing between cache: 'no-store' and next: { revalidate: N } depends on your data's needs:

• no-store: Use for data that must be absolutely fresh on every request (e.g., real-time stock prices, user-specific shopping cart).
• revalidate: N: Use for data that can be slightly stale but should update periodically (e.g., blog posts, product listings that change hourly).
• Default (cached): Use for static or infrequently changing data (e.g., navigation links, static page content).

While fetch is powerful for external APIs, Server Components can also directly interact with databases or ORMs like Prisma. Since Server Components run on the server, they can safely contain database credentials.

This means you can write code like await prisma.user.findMany() directly in your components, keeping your client bundle small and secure.

You've learned how to harness server-side data fetching in Next.js 15!

• fetch in Server Components is automatically optimized with caching.
• Use cache: 'no-store' for always-fresh data.
• Use next: { revalidate: N } for time-based data freshness.
• Server Components can also directly access databases securely.

Mastering these techniques is key to building fast, efficient, and secure Next.js applications.