Cache invalidation strategies in NextJS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is cache invalidation in Next.js?

Cache invalidation is the process of updating or removing stored data so users see fresh content instead of outdated information.

beginner

Explain the 'Time-based' cache invalidation strategy.

Time-based invalidation removes or refreshes cached data after a set time, ensuring content updates regularly without manual intervention.

intermediate

What is 'On-demand' cache invalidation in Next.js?

On-demand invalidation lets you manually clear or update cache when data changes, often using API routes or server actions to trigger refresh.

intermediate

How does Next.js support cache invalidation with Incremental Static Regeneration (ISR)?

ISR allows pages to be statically generated and then updated in the background after a set time, combining fast load with fresh content.

beginner

Why is cache invalidation important in web apps?

It keeps user data fresh, improves performance by avoiding unnecessary reloads, and prevents showing outdated or wrong information.

Which Next.js feature helps update static pages after deployment without rebuilding the whole site?

A Static Site Generation (SSG)

B Incremental Static Regeneration (ISR)

C Client-side Rendering (CSR)

D Server-side Rendering (SSR)

ISR allows static pages to update after deployment by regenerating them in the background.

What does 'time-based' cache invalidation rely on?

A Manual user action

B Data change detection

C A set expiration time

D Random cache clearing

Time-based invalidation uses a set expiration time to refresh cache automatically.

Which method lets you clear cache manually in Next.js?

A Static generation

B Time-based invalidation

C Automatic cache refresh

D On-demand invalidation

On-demand invalidation allows manual cache clearing when data changes.

Why avoid never invalidating cache in a web app?

A It shows outdated data

B It improves performance

C It reduces server load

D It speeds up page loads

Never invalidating cache can cause users to see outdated or wrong information.

What is a common tool to trigger on-demand cache invalidation in Next.js?

A API routes

B Static files

C CSS modules

D Client-side hooks

API routes can be used to trigger cache clearing or regeneration on demand.

Describe three cache invalidation strategies used in Next.js and when to use each.

Think about how and when cached data should update.

Explain why cache invalidation is important for user experience in web applications.

Consider what happens if cache never updates.

Practice

1. In Next.js, which method allows you to update static pages after a certain time interval to keep data fresh without rebuilding the entire site?

easy

A. getServerSideProps without caching

B. Manually clearing browser cache

C. Using client-side useEffect to fetch data

D. getStaticProps with revalidate

Solution

1. Step 1: Understand Next.js data fetching methods

   getStaticProps generates static pages at build time, but with revalidate, it can update pages after a set interval.

2. Step 2: Compare with other methods

   getServerSideProps fetches fresh data on every request but does not use caching or revalidation intervals.

3. Final Answer:

   getStaticProps with revalidate -> Option D

4. Quick Check:

   Incremental Static Regeneration = getStaticProps + revalidate [OK]

Hint: Remember: revalidate updates static pages periodically [OK]

Common Mistakes:

• Confusing getServerSideProps with revalidation
• Thinking client-side fetching is cache invalidation
• Assuming manual browser cache clearing affects server cache

2. Which of the following is the correct way to set a revalidation time of 10 seconds in getStaticProps?

easy

A. return { props: {}, revalidate: 10 }

B. return { props: {}, revalidateTime: 10 }

C. return { props: {}, cache: 10 }

D. return { props: {}, refresh: 10 }

Solution

1. Step 1: Recall the correct property name for revalidation

   The Next.js documentation specifies revalidate as the property to set seconds for incremental static regeneration.

2. Step 2: Check the return object structure

   The return object from getStaticProps must include props and optionally revalidate with a number value.

3. Final Answer:

   return { props: {}, revalidate: 10 } -> Option A

4. Quick Check:

   Property name is revalidate [OK]

Hint: Use exact property name 'revalidate' in return object [OK]

Common Mistakes:

• Using incorrect property names like 'revalidateTime' or 'refresh'
• Placing revalidate outside the return object
• Setting revalidate as a string instead of a number

3. Consider this Next.js code snippet:

export async function getStaticProps() {
  return {
    props: { time: Date.now() },
    revalidate: 5
  };
}

What will happen if you visit this page multiple times within 5 seconds?

medium

A. The page will throw an error due to Date.now() in getStaticProps

B. The page will show the same timestamp for all visits within 5 seconds

C. The page will update the timestamp on every visit

D. The page will never update the timestamp

Solution

1. Step 1: Understand revalidate behavior

   The revalidate: 5 means Next.js will regenerate the page at most every 5 seconds.

2. Step 2: Predict output within 5 seconds

   Within 5 seconds, the cached page is served, so the timestamp remains the same for all visits.

3. Final Answer:

   The page will show the same timestamp for all visits within 5 seconds -> Option B

4. Quick Check:

   Revalidate interval caches page for 5 seconds [OK]

Hint: Revalidate caches page until interval expires [OK]

Common Mistakes:

• Assuming timestamp updates on every visit
• Thinking Date.now() causes errors in static props
• Believing revalidate disables caching

4. You wrote this code in Next.js:

export async function getStaticProps() {
  return {
    props: { data: await fetchData() },
    revalidate: '10'
  };
}

Why does this cause a problem?

medium

A. Because revalidate must be a number, not a string

B. Because fetchData cannot be awaited in getStaticProps

C. Because props must be a function, not an object

D. Because revalidate cannot be used with getStaticProps

Solution

1. Step 1: Check the type of revalidate

   The revalidate property expects a number representing seconds, not a string.

2. Step 2: Understand impact of wrong type

   Passing a string causes Next.js to throw a type error or ignore the revalidation, breaking cache invalidation.

3. Final Answer:

   revalidate must be a number, not a string -> Option A

4. Quick Check:

   Revalidate value type = number [OK]

Hint: Use number type for revalidate seconds [OK]

Common Mistakes:

• Passing revalidate as a string
• Thinking async/await is disallowed in getStaticProps
• Confusing props structure requirements

5. You want to always serve fresh data on every request in Next.js without caching. Which method should you use and why?

hard

A. Use getStaticProps without revalidate

B. Use getStaticProps with revalidate: 0

C. Use getServerSideProps because it runs on every request

D. Use client-side fetching only with useEffect

Solution

1. Step 1: Identify method for fresh data every request

   getServerSideProps runs on the server for every page request, ensuring fresh data.

2. Step 2: Compare with static methods

   getStaticProps generates static pages at build time or with revalidation intervals, so it does not guarantee fresh data every request.

3. Final Answer:

   Use getServerSideProps because it runs on every request -> Option C

4. Quick Check:

   Fresh data every request = getServerSideProps [OK]

Hint: Always fresh data? Use getServerSideProps [OK]

Common Mistakes:

• Using revalidate: 0 expecting no caching
• Relying only on client-side fetching for SEO
• Confusing static and server-side methods