0Pricing
Next.js 15 Fullstack (App Router + Server Actions) · Pelajaran

Penyimpanan Sementara & Validasi Ulang

Pahami mekanisme penyimpanan sementara Next.js yang andal serta cara memvalidasi ulang data tersimpan agar konten tetap terbaru.

Penyimpanan Sementara & Validasi Ulang adalah pelajaran Next.js 15 Fullstack (App Router + Server Actions) gratis di CoddyKit. Ini adalah pelajaran 2 dari 3. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Next.js 15 Fullstack (App Router + Server Actions), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Next.js 15 Fullstack (App Router + Server Actions) mencakup 3 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Why Caching Matters

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.

Built-in Data Cache

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.

`fetch` Defaults in Server Components

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.

Try Default Caching

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.

// app/page.js
async function getUserData() {
  // This fetch request is automatically cached by Next.js
  const res = await fetch('https://jsonplaceholder.typicode.com/users/1');
  if (!res.ok) {
    throw new Error('Failed to fetch user data');
  }
  return res.json();
}

export default async function HomePage() {
  const user = await getUserData();
  return (
    <div>
      <h1>User Profile</h1>
      <p>Name: {user.name}</p>
      <p>Email: {user.email}</p>
      <p>Fetched at: {new Date().toLocaleTimeString()}</p>
    </div>
  );
}

Bypassing the Cache

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.

Try Bypassing Cache

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

// app/live-data/page.js
async function getLiveTime() {
  // This fetch request explicitly opts out of caching
  const res = await fetch('https://worldtimeapi.org/api/ip', {
    cache: 'no-store', // Always re-fetch
  });
  if (!res.ok) {
    throw new Error('Failed to fetch live time');
  }
  return res.json();
}

export default async function LiveDataPage() {
  const timeData = await getLiveTime();
  return (
    <div>
      <h1>Live Time</h1>
      <p>Current time in your timezone:</p>
      <p><b>{new Date(timeData.datetime).toLocaleTimeString()}</b></p>
      <p>Last fetched: {new Date().toLocaleTimeString()}</p>
    </div>
  );
}

Revalidating Data Over Time

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.

Try Time-based Revalidation

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.

// app/revalidated-data/page.js
async function getRevalidatedData() {
  // Data will be revalidated every 10 seconds
  const res = await fetch('https://worldtimeapi.org/api/timezone/Etc/UTC', {
    next: { revalidate: 10 }, // Revalidate after 10 seconds
  });
  if (!res.ok) {
    throw new Error('Failed to fetch revalidated data');
  }
  return res.json();
}

export default async function RevalidatedPage() {
  const data = await getRevalidatedData();
  return (
    <div>
      <h1>Revalidated UTC Time</h1>
      <p>Current UTC Time: <b>{new Date(data.datetime).toLocaleTimeString()}</b></p>
      <p>This data revalidates every 10 seconds.</p>
      <p>Last rendered: {new Date().toLocaleTimeString()}</p>
    </div>
  );
}

Manual Revalidation

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.

Test Your Knowledge

Which of the following Next.js fetch options ensures that data is ALWAYS fetched from the origin server on every request, bypassing any cache?

Caching & Revalidation Recap

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!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Penyimpanan Sementara & Validasi Ulang” gratis?

Ya — teks lengkap “Penyimpanan Sementara & Validasi Ulang” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Next.js 15 Fullstack (App Router + Server Actions), upgrade ke CoddyKit PRO. Kursus Next.js 15 Fullstack (App Router + Server Actions) mencakup 3 pelajaran total.

Apa yang akan aku pelajari di “Penyimpanan Sementara & Validasi Ulang”?

Pahami mekanisme penyimpanan sementara Next.js yang andal serta cara memvalidasi ulang data tersimpan agar konten tetap terbaru. Kamu berlatih Next.js 15 Fullstack (App Router + Server Actions) dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Next.js 15 Fullstack (App Router + Server Actions)?

Tidak diperlukan pengalaman sebelumnya. Next.js 15 Fullstack (App Router + Server Actions) di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 3.

Berapa lama pelajaran “Penyimpanan Sementara & Validasi Ulang” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Next.js 15 Fullstack (App Router + Server Actions) ini?

Ya. Setiap pelajaran Next.js 15 Fullstack (App Router + Server Actions) menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Pengambilan Data Sisi Server
  2. Penyimpanan Sementara & Validasi Ulang
  3. Pengambilan Data Paralel, Berurutan, dan Streaming
← Kembali ke Next.js 15 Fullstack (App Router + Server Actions)