Loading and caching data

What this means

Next.js can load data in server components, route handlers, or client components. The right choice depends on security, freshness, and interaction needs.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

Good data boundaries prevent secrets from reaching browsers and make loading states predictable.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

const response = await fetch(url, { cache: "no-store" });

Common mistake

Do not put private API keys into client-side code.

Practice task

Choose where public track data and private account data should load.

Remember this

Load trusted data on the server and show explicit loading states.