Dene telung strategi utama kanggo kapan HTML halaman digawe. Nggoleki sing pas saben halaman ngewangi perimbangan antara kanyar, performa, lan biaya server.
() {
posts = (, { : }).( r.());
;
}
Halaman dipregawe bedhé dadi HTML statis ing build lan disimpen ing CDN. Pangpaling cepet kanggo kiriman, nanging isi mau kebeku nganti build sabanjure. Paling apik kanggo konten sing arang owah: halaman marketing, dokumentasi, artikel blog.
// HTML generated FRESH on every request
export default async function Page() {
const data = await fetch("...", { cache: "no-store" }).then(r => r.json());
return <Dashboard data={data} />;
}
Server nggawe halaman saben panjaluk teka, dadi data mesthi kanyar — nanging kanthi biaya respon sing lambat lan beban server saben kunjungan. Paling apik kanggo data sing personal utawa mesthi kanyar: dashboard, halaman akun, asil pencarian.
// Static, but automatically rebuilt in the background every N seconds
export const revalidate = 60; // regenerate at most once per 60s
export default async function Page() {
const products = await fetch("...", { next: { revalidate: 60 } }).then(r => r.json());
return <Products items={products} />;
}
ISR melayani HTML statis (cepet, disimpen CDN) nanging revalidasi dhéwé ing latar ngarep ing jadwal — mula sampeyan ngoleh performa statis karo data sing periodik kanyar, tanpa bangun maneh kabeh situs. Paling apik kanggo konten sing owah kadang-kadang: daftar produk, warta, papan peringkat.
Speed Freshness Server cost Use for
SSG fastest build-time only none docs, marketing
SSR slower always fresh every request dashboards, personalized
ISR fast every N seconds occasional catalogs, news
Ing App Router sampeyan pilih iki saben-saben fetch via opsyen cache (force-cache = SSG, no-store = SSR, revalidate = ISR) tinimbang fungsi khusus.
Ngerti perimbangan iku — statis paling cepet nanging lawas, SSR kanyar nanging larang, ISR ngewangi loro — nglilani sampeyan optimalake saben halaman kanggo kombinasi performa lan kanyarnya data sing pas.