การแคชและการตรวจสอบใหม่

Caching is a fundamental technique to improve the performance and responsiveness of web applications.

Imagine fetching the same data repeatedly from a database or an API. This creates unnecessary load and slows down your app.

Caching stores a copy of frequently accessed data, so it can be served faster on subsequent requests, reducing latency and resource usage.

Next.js 15, especially with the App Router, comes with powerful built-in caching mechanisms.

• It intelligently caches data fetched using the native fetch API within Server Components.
• This cache is stored on the server, ensuring faster responses for repeat visitors or multiple requests for the same data.
• It helps your application deliver content quickly without constant re-fetching.

When you use the standard fetch API inside a Next.js Server Component, Next.js automatically caches the data.

This means if the same fetch request is made again, Next.js will serve the data from its cache instead of hitting the external API.

This behavior is optimized for scenarios where data doesn't change frequently and can significantly boost performance.

Here's a simple example of a Server Component fetching data. Notice how Next.js caches the result implicitly.

If you were to run this and refresh, the fetch call might not hit the external API again immediately, depending on the cache lifetime.

Sometimes, you need to ensure data is always fresh and not served from the cache. For instance, when displaying real-time stock prices or user-specific data that changes often.

You can opt out of caching for a specific fetch request by setting the cache option to 'no-store'.

• fetch('...', { cache: 'no-store' }) tells Next.js to always re-fetch data.
• This ensures you get the latest information every time.

This example demonstrates how to explicitly bypass the cache. Each time this component renders, a new request will be made to the API.

What if you want data to be cached but refresh after a certain period? Next.js supports time-based revalidation, similar to Incremental Static Regeneration (ISR).

You can specify a revalidate option within the next property of your fetch call:

• fetch('...', { next: { revalidate: 60 } }) will cache the data for 60 seconds.
• After 60 seconds, the next request will trigger a re-fetch in the background, serving stale data first, then fresh data.

In this example, the data will be cached for 10 seconds. If you refresh the page within 10 seconds, you'll see the cached time. After 10 seconds, a new fetch will occur.

Beyond time-based revalidation, Next.js also allows you to revalidate cached data manually, or "on-demand".

• revalidatePath('/path'): Revalidates the cache for a specific page path.
• revalidateTag('tag'): Revalidates all fetch requests that were tagged with a specific string (e.g., fetch('...', { next: { tags: ['products'] } })).

This is useful when data changes due to a user action (e.g., updating a product) and you want to ensure the UI shows the latest information immediately.

In this lesson, you learned about Next.js's powerful data caching mechanisms.

• Next.js caches fetch requests in Server Components by default.
• You can bypass the cache with { cache: 'no-store' } for real-time data.
• Time-based revalidation (ISR) is achieved with { next: { revalidate: N } }.
• On-demand revalidation uses revalidatePath or revalidateTag to manually refresh cached data.

Mastering these techniques is crucial for building high-performance Next.js applications!