Next.js 15 Fullstack (App Router + Server Actions) · Lesson

Managing Server State

Explore strategies for managing server-fetched data and keeping it synchronized with your UI, including SWR or React Query.

Managing Server State is a free Next.js 15 Fullstack (App Router + Server Actions) lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Next.js 15 Fullstack (App Router + Server Actions) learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

What is Server State?

When building applications, you deal with different kinds of data. Server state refers to data that lives on a remote server, like a list of products, user profiles, or blog posts.

It's distinct from client state, which is data managed purely within your application, such as whether a modal is open or a theme is dark/light.

Challenges of Server State

Managing server state can be tricky because:

It's Asynchronous: Data isn't instantly available; it takes time to fetch.
It Can Be Stale: The data on the server might change after you've fetched it.
Caching is Hard: How do you store fetched data efficiently and know when to refetch?
Error Handling: Network requests can fail, requiring robust error management.
Loading States: Users need feedback while data is being fetched.

Introducing SWR & React Query

Libraries like SWR (Stale-While-Revalidate) and React Query (now TanStack Query) are designed specifically to tackle these server state challenges in React applications.

They provide powerful hooks that simplify data fetching, caching, revalidation, and error handling, making your UI more robust and responsive.

Simple Asynchronous Fetch

Before using a library like SWR, fetching data asynchronously often involves manual handling of loading, success, and error states. Here's a basic JavaScript example:

async function fetchData() {
  console.log("Fetching data...");
  try {
    const response = await fetch('https://jsonplaceholder.typicode.com/todos/1');
    if (!response.ok) {
      throw new Error(`HTTP error! status: ${response.status}`);
    }
    const data = await response.json();
    console.log("Data fetched: ", data.title);
  } catch (error) {
    console.error("Fetch error: ", error.message);
  }
}

fetchData();

The useSWR Hook

SWR wraps this fetching logic into a convenient React Hook called useSWR. It automatically provides the data, error, and a loading state (implicitly via data being undefined initially).

You provide a unique key (often the API endpoint) and a fetcher function that makes the actual data request.

import useSWR from 'swr';

const fetcher = url => fetch(url).then(res => res.json());

function UserProfile() {
  // The key is '/api/user', the fetcher is our function
  const { data, error } = useSWR('/api/user', fetcher);

  if (error) return <div>Failed to load user.</div>;
  if (!data) return <div>Loading user...</div>;

  return <div>Hello, {data.name}!</div>;
}
// In a Next.js app, UserProfile would be rendered
// inside a page component.

Smart Caching & Deduping

One of SWR's core features is its intelligent caching. When multiple components request data with the same key, SWR automatically deduplicates these requests, fetching the data only once.

It then shares this cached data across all subscribers, preventing unnecessary network calls and improving performance. This is crucial for large applications.

Stale-While-Revalidate Strategy

SWR's name comes from its Stale-While-Revalidate caching strategy. This means:

It immediately returns the cached (stale) data to the UI.
It then sends a request to revalidate (fetch new) data in the background.
Once new data arrives, it updates the UI.

This provides an instant user experience while ensuring data freshness.

Automatic Revalidation

SWR and React Query automatically revalidate data in several common scenarios, ensuring your UI always reflects the latest server state:

On Focus: When the browser tab or window regains focus.
On Reconnect: When the network connection is restored.
On Interval: You can configure periodic revalidation for frequently changing data.

This significantly reduces the need for manual data refreshing.

Mutating Data & UI Updates

When you perform actions that change server data (e.g., submitting a form to create a new post), you need to update your UI. SWR provides a mutate function to help with this.

You can use mutate to manually revalidate the data associated with a key, or even update the local cache directly for immediate optimistic UI updates.

Server State Check

Which of the following are key benefits of using a library like SWR or React Query for managing server state?

Recap & Next Steps

You've explored the world of server state and learned why it requires special handling compared to client state. Libraries like SWR and React Query are indispensable tools for Next.js developers, simplifying data fetching, caching, revalidation, and error management.

By leveraging these libraries, you can build more performant, reliable, and user-friendly applications with less effort. Keep practicing these concepts to master your data fetching!

Frequently asked questions

Is the “Managing Server State” lesson free?

Yes — the full text of “Managing Server State” is free to read here on the web, and the Next.js 15 Fullstack (App Router + Server Actions) course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Next.js 15 Fullstack (App Router + Server Actions) course, upgrade to CoddyKit PRO.

What will I learn in “Managing Server State”?

Explore strategies for managing server-fetched data and keeping it synchronized with your UI, including SWR or React Query. You practise Next.js 15 Fullstack (App Router + Server Actions) with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Next.js 15 Fullstack (App Router + Server Actions)?

No prior experience is required. Next.js 15 Fullstack (App Router + Server Actions) on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Managing Server State” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Next.js 15 Fullstack (App Router + Server Actions) lesson?

Yes. Every Next.js 15 Fullstack (App Router + Server Actions) lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Next.js 15 Fullstack (App Router + Server Actions)