Why Revalidation strategies (time-based) in NextJS? - Purpose & Use Cases

The Big Idea

What if your site could update itself automatically without slowing down visitors?

The Scenario

Imagine you have a website that shows news articles. Every time someone visits, you fetch fresh data manually by calling the server. If many people visit at once, your server gets overwhelmed and the site feels slow.

The Problem

Manually fetching fresh data on every visit is slow and costly. It can cause delays, overload servers, and users might see outdated content if caching is not handled well.

The Solution

Time-based revalidation lets Next.js automatically refresh cached pages after a set time. This keeps content fresh without slowing down users or overloading servers.

Before vs After

✗ Before

fetch('/api/data') on every page load

✓ After

export const revalidate = 60; // refresh data every 60 seconds

What It Enables

This makes your site fast, scalable, and always up-to-date without extra work.

Real Life Example

A blog that updates its homepage every minute to show the latest posts without making visitors wait.

Key Takeaways

Manual data fetching on every visit is slow and costly.

Time-based revalidation automates refreshing cached content.

This keeps sites fast and fresh for all users.