Caching API responses in Astro

Introduction

Caching API responses helps your website load faster by saving data from previous requests. This means users don't have to wait for the same information to be fetched again.

When your website shows data that doesn't change often, like weather or news headlines.

When you want to reduce the number of requests to a slow or limited API.

When you want to improve user experience by making pages load quickly.

When you want to save bandwidth and server resources.

When you want to handle temporary network issues gracefully by showing cached data.

Syntax

Astro

export const revalidate = 3600;

export default async function Page() {
  const response = await fetch('https://api.example.com/data');
  const data = await response.json();

  return (
    <div>{/* use {data} here */}</div>
  );
}

revalidate tells Astro how many seconds to keep the cached data before fetching fresh data.

This example uses an async page component to fetch data at prerender time and cache it.

Examples

Cache user data for 10 minutes to reduce API calls.

Astro

export const revalidate = 600; // cache for 10 minutes

export default async function Page() {
  const response = await fetch('https://api.example.com/users');
  const users = await response.json();

  return (
    <div>{/* use {users} here */}</div>
  );
}

Cache blog posts for 24 hours since they change rarely.

Astro

export const revalidate = 86400; // cache for 24 hours

export default async function Page() {
  const response = await fetch('https://api.example.com/posts');
  const posts = await response.json();

  return (
    <div>{/* use {posts} here */}</div>
  );
}

Cache weather data for 5 minutes to keep it fresh but reduce calls.

Astro

export const revalidate = 300; // cache for 5 minutes

export default async function Page() {
  const response = await fetch('https://api.example.com/weather');
  const weather = await response.json();

  return (
    <div>{/* use {weather} here */}</div>
  );
}

Sample Program

This Astro component fetches product data from an API and caches it for 30 minutes. When users visit the page, they see the product list quickly without waiting for a fresh API call every time.

Astro

export const revalidate = 1800; // cache for 30 minutes

export default async function ProductsPage() {
  const response = await fetch('https://api.example.com/products');
  const products = await response.json();

  return (
    <main>
      <h1>Product List</h1>
      <ul>
        {products.map(product => (
          <li key={product.id}>{product.name} - ${product.price}</li>
        ))}
      </ul>
    </main>
  );
}

Important Notes

Use caching to balance fresh data and fast loading times.

Set revalidate time based on how often your data changes.

Cached data is stored on the server, so users get faster responses.

Summary

Caching API responses speeds up your site by saving data from previous requests.

Use export const revalidate in your page component to control cache duration.

Choose cache time based on how often your data updates.

Practice

1. What is the main benefit of caching API responses in Astro?

easy

A. It speeds up the site by reusing previously fetched data

B. It increases the size of the API response

C. It makes the API slower to respond

D. It disables the API from updating

Solution

1. Step 1: Understand caching purpose

   Caching stores data from previous API calls to avoid fetching again.

2. Step 2: Identify benefit in Astro context

   Reusing cached data reduces load time and speeds up the site.

3. Final Answer:

   It speeds up the site by reusing previously fetched data -> Option A

4. Quick Check:

   Caching = Speed up site [OK]

Hint: Caching saves time by reusing data, not slowing down [OK]

Common Mistakes:

• Thinking caching makes API slower
• Confusing cache with data size increase
• Believing cache disables updates

2. Which syntax correctly sets cache revalidation time in Astro?

easy

A. const data = await fetch('https://api.example.com/data', { refresh: 60 });

B. const data = await fetch('https://api.example.com/data', { cacheTime: 60 });

C. const data = await fetch('https://api.example.com/data', { revalidate: 60 });

D. const data = await fetch('https://api.example.com/data', { updateAfter: 60 });

Solution

1. Step 1: Recall correct property name

   The correct property to control cache duration is revalidate.

2. Step 2: Match syntax with Astro docs

   The syntax uses { revalidate: 60 } inside fetch().

3. Final Answer:

   const data = await fetch('https://api.example.com/data', { revalidate: 60 }); -> Option C

4. Quick Check:

   Use revalidate property = const data = await fetch('https://api.example.com/data', { revalidate: 60 }); [OK]

Hint: Remember 'revalidate' sets cache time in seconds [OK]

Common Mistakes:

• Using wrong property names like cacheTime or refresh
• Forgetting to return an object
• Placing revalidate outside return

3. Given this code snippet in Astro:

const data = await fetch('https://api.example.com/data', { revalidate: 120 }).then(res => res.json());

What happens when a user visits the page after 3 minutes?

medium

A. The cached data is used without fetching again

B. The cache is cleared but data is not fetched

C. The page shows an error due to cache expiry

D. The data is fetched again from the API

Solution

1. Step 1: Understand revalidate timing

   The revalidate: 120 means cache lasts 120 seconds (2 minutes).

2. Step 2: Compare visit time with cache duration

   After 3 minutes (180 seconds), cache expired, so Astro fetches fresh data.

3. Final Answer:

   The data is fetched again from the API -> Option D

4. Quick Check:

   Cache expired after 120s, fetch again [OK]

Hint: If visit time > revalidate, data refetches [OK]

Common Mistakes:

• Assuming cache lasts forever
• Thinking cache clears but no fetch happens
• Confusing cache expiry with errors

4. Identify the error in this Astro caching code:

const data = await fetch('https://api.example.com/data').json();

medium

A. Missing await before .json() call

B. Incorrect property name 'revalidate'

C. fetch URL is invalid

D. Return statement missing props object

Solution

1. Step 1: Check fetch usage

   fetch returns a Promise; calling .json() needs to await the fetch first.

2. Step 2: Identify missing await

   Code calls fetch(...).json() without awaiting fetch, causing error.

3. Final Answer:

   Missing await before .json() call -> Option A

4. Quick Check:

   Await fetch before .json() [OK]

Hint: Always await fetch before calling .json() [OK]

Common Mistakes:

• Calling .json() directly on fetch without await
• Misnaming revalidate property
• Assuming fetch URL is wrong without checking

5. You want to cache API data in Astro but update it every hour. Which is the best way to set revalidate and why?

Options:
A) revalidate: 3600 to update every hour
B) revalidate: 60 to update every minute
C) revalidate: 0 to never cache
D) revalidate: -1 to disable caching

hard

A. revalidate: 60 to update every minute

B. revalidate: 3600 to update every hour

C. revalidate: 0 to never cache

D. revalidate: -1 to disable caching

Solution

1. Step 1: Understand revalidate meaning

   revalidate sets cache duration in seconds before refreshing data.

2. Step 2: Match desired update frequency

   To update every hour, set revalidate to 3600 seconds (60*60).

3. Step 3: Evaluate other options

   60 seconds updates too often, 0 disables caching, -1 is invalid.

4. Final Answer:

   revalidate: 3600 to update every hour -> Option B

5. Quick Check:

   1 hour = 3600 seconds revalidate [OK]

Hint: Set revalidate in seconds matching update frequency [OK]

Common Mistakes:

• Using too short revalidate causing frequent fetches
• Setting zero disables caching, not hourly update
• Negative values are invalid