Static vs server-side data fetching in Astro - Quick Revision & Key Differences

Recall & Review

beginner

What is static data fetching in Astro?

Static data fetching means getting data at build time. The data is fetched once when the site is built, then saved as static files. This makes pages load very fast because no server work is needed when users visit.

beginner

What does server-side data fetching mean in Astro?

Server-side data fetching means getting data when a user requests a page. The server fetches fresh data each time, then sends the page. This is good for data that changes often.

beginner

Name one advantage of static data fetching.

Pages load very fast because data is already included in the built files. No waiting for server responses on each visit.

beginner

Why might you choose server-side data fetching over static?

If your data changes often or depends on the user, server-side fetching gives fresh data every time the page loads.

intermediate

How does Astro let you choose between static and server-side data fetching?

Astro uses special functions like getStaticPaths for static and server-only code for server-side fetching. You pick based on your data needs.

When is static data fetched in Astro?

A Only when the server restarts

B On every user request

C At build time

D When the user clicks a button

Static data fetching happens once during the build process, so data is ready before users visit.

Which data fetching method gives the freshest data on each page load?

A Static data fetching

B None of the above

C Client-side data fetching

D Server-side data fetching

Server-side fetching gets data when the page is requested, so it is always up to date.

What is a downside of server-side data fetching?

A Pages load slower because data is fetched on each request

B Data is never updated

C It only works for static sites

D It cannot fetch data from APIs

Fetching data on every request adds delay before the page shows.

Which Astro function is used for static data fetching?

A getServerSideProps

B getStaticPaths

C useEffect

D fetchData

getStaticPaths helps fetch data at build time for static pages.

If your site data rarely changes, which fetching method is best?

A Static data fetching

B No data fetching

C Client-side fetching

D Server-side data fetching

Static fetching is best for rarely changing data because it makes pages fast and simple.

Explain the difference between static and server-side data fetching in Astro.

Think about when the data is fetched and how it affects page speed and freshness.

When would you choose server-side data fetching over static in a real website?

Consider websites like news or user dashboards.

Practice

1. What is the main difference between static data fetching and server-side data fetching in Astro?

easy

A. Both fetch data only once at build time.

B. Static fetching gets data on every request; server-side fetching gets data once at build time.

C. Both fetch data on every request.

D. Static fetching gets data once at build time; server-side fetching gets data on every request.

Solution

1. Step 1: Understand static data fetching

   Static fetching means data is fetched once during the build process, so pages load very fast but data stays the same until next build.

2. Step 2: Understand server-side data fetching

   Server-side fetching means data is fetched fresh on every user request, so content is always up-to-date but slower to load.

3. Final Answer:

   Static fetching gets data once at build time; server-side fetching gets data on every request. -> Option D

4. Quick Check:

   Static = build time, Server-side = request time [OK]

Hint: Static = build once, Server-side = fetch every request [OK]

Common Mistakes:

• Confusing when data is fetched
• Thinking static fetches on every request
• Assuming server-side fetches only once

2. Which of the following is the correct syntax to fetch data statically in an Astro component?

easy

A. export async function getStatic() { const data = await fetchData(); return { data } }

B. export async function getStaticProps() { return { props: { data } } }

C. export async function getStaticPaths() { return { paths: [] } }

D. export async function getStatic() { return { props: { data } } }

Solution

1. Step 1: Identify Astro static data fetching syntax

   Astro uses getStaticPaths to fetch data at build time and generate static paths.

2. Step 2: Check options for correct function and return structure

   export async function getStaticPaths() { return { paths: [] } } correctly defines getStaticPaths returning paths. Others use wrong function names or incomplete returns.

3. Final Answer:

   export async function getStaticPaths() { return { paths: [] } } -> Option C

4. Quick Check:

   Static fetch uses getStaticPaths [OK]

Hint: Static fetch uses getStaticPaths with paths return [OK]

Common Mistakes:

• Using wrong function names like getStatic
• Returning data without paths wrapper
• Using getStaticProps which is from Next.js

3. Given this Astro server-side fetch code snippet, what will be the output if the API returns {"message": "Hello"}?

export async function GET({ params }) {
  const res = await fetch('https://api.example.com/greet');
  const data = await res.json();
  return {
    body: JSON.stringify({ greeting: data.message })
  };
}

medium

A. {"greeting":"Hello"}

B. {"message":"Hello"}

C. Error: fetch is not defined

D. {"greet":"Hello"}

Solution

1. Step 1: Analyze the fetch and JSON parsing

   The code fetches from the API, parses JSON, and extracts the 'message' field which is "Hello".

2. Step 2: Check the returned body structure

   The returned body is a JSON string with key 'greeting' set to data.message, so output is {"greeting":"Hello"}.

3. Final Answer:

   {"greeting":"Hello"} -> Option A

4. Quick Check:

   Returned JSON key is greeting with value Hello [OK]

Hint: Returned JSON keys match code's object keys [OK]

Common Mistakes:

• Confusing returned keys with API keys
• Expecting raw API response instead of transformed
• Assuming fetch error without context

4. Identify the error in this Astro server-side data fetching code:

export async function GET() {
  const response = await fetch('https://api.example.com/data');
  const data = await response.json;
  return {
    body: JSON.stringify(data)
  };
}

medium

A. Missing parentheses after json method call

B. fetch URL is incorrect

C. Return statement should use props instead of body

D. Function should be named getStaticProps

Solution

1. Step 1: Check the fetch and JSON parsing syntax

   The code calls response.json without parentheses, which is a function and must be called as response.json().

2. Step 2: Validate other parts of the code

   The fetch URL looks valid, returning body is correct for server-side, and function name GET is valid for server-side fetch in Astro.

3. Final Answer:

   Missing parentheses after json method call -> Option A

4. Quick Check:

   json() needs parentheses to execute [OK]

Hint: Call json() with parentheses to parse response [OK]

Common Mistakes:

• Forgetting parentheses on json()
• Confusing server-side and static function names
• Using wrong return structure for server-side

5. You want to build a blog with Astro where posts rarely change. Which data fetching method should you use and why? export async function getStaticPaths() { ... } or export async function GET()?

hard

A. Use GET to fetch posts on every request to ensure always fresh content.

B. Use getStaticPaths to fetch posts once at build time for faster load and stable content.

C. Use getStaticPaths but fetch data on every request inside it.

D. Use GET and cache the data manually to simulate static fetching.

Solution

1. Step 1: Understand blog content update frequency

   Since posts rarely change, fetching once at build time is efficient and fast.

2. Step 2: Match fetching method to content needs

   getStaticPaths fetches data once at build time, ideal for stable content. GET fetches on every request, unnecessary here.

3. Final Answer:

   Use getStaticPaths to fetch posts once at build time for faster load and stable content. -> Option B

4. Quick Check:

   Rarely changing data = static fetch [OK]

Hint: Rarely changing data? Use static fetch for speed [OK]

Common Mistakes:

• Choosing server-side fetch for stable data
• Mixing fetch methods incorrectly
• Trying to fetch every request inside static method