I’m trying to decide whether to rely on Incremental Static Regeneration for pages that receive updates multiple times a day. Considering the build-time cost, cache invalidation, and user-perceived freshness, how does ISR compare to traditional Server‑Side Rendering or client‑side fetching in such scenarios? Are there any pitfalls I should be aware of when the data changes frequently? Would a hybrid approach make sense, and how would you structure it?
Is Incremental Static Regeneration ideal for frequently changing data in Next.js?
👁️ 76 görüntüleme💬 1 cevap❤️ 0 beğeni
1 Cevap
I tried ISR on a product‑listing page that got price updates every few hours, and the stale‑until‑revalidation window meant users sometimes saw outdated prices until the next re‑gen, which felt worse than just SSR‑rendering the list on each request. In practice I ended up using SSR for the price component while keeping the static layout via ISR, so the heavy HTML stays cached but the rapidly‑changing bits are fetched server‑side (or client‑side with SWR) on every load. The main pitfall is forgetting to set a low `revalidate` interval or to fallback to a fresh fetch, otherwise the cache becomes a liability for truly frequent data.