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

Mutating Data & Revalidation

Learn how Server Actions can mutate data on the server and automatically revalidate cached data to update the UI.

Mutating Data & Revalidation is a free Next.js 15 Fullstack (App Router + Server Actions) lesson on CoddyKit — lesson 2 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 Data Mutation?

In web development, data mutation means changing data on the server. This includes creating new data, updating existing records, or deleting data.

  • Create: Adding a new user.
  • Update: Changing a user's email.
  • Delete: Removing an item from a list.

Most interactive web applications rely heavily on data mutation to provide dynamic experiences.

Server Actions for Mutations

Next.js 15's Server Actions are perfect for handling data mutations. They allow you to run server-side code directly from your React components, making it simple to update your backend.

Instead of creating API routes for every data change, you can define these actions right where they're needed, keeping your code organized and efficient.

The Cache Challenge

When you mutate data on the server, the client-side UI often doesn't automatically reflect these changes. This is because Next.js (and browsers) aggressively cache data to improve performance.

If the UI still shows old, cached data after a server update, users see outdated information. We need a way to tell Next.js: "Hey, this data has changed, please get the fresh version!"

Revalidating with `revalidatePath`

To ensure your UI shows the latest data, Next.js provides caching utilities. One common method is revalidatePath.

After a Server Action changes data, you can call revalidatePath('/') to tell Next.js to invalidate the cache for the specified path (e.g., the home page) and refetch its data on the next request.

Demo: Update & Revalidate Path

This example shows a simple form that adds a task using a Server Action. After the task is added, revalidatePath('/') ensures that any data displayed on the root page (like a list of tasks) is refreshed.

import { revalidatePath } from 'next/cache';

async function addTask(formData) {
  'use server';
  const task = formData.get('task');
  // Simulate saving to a database
  console.log('Adding task:', task);
  await new Promise(r => setTimeout(r, 500));

  // Revalidate the home page to show new tasks
  revalidatePath('/');
}

export default function Page() {
  return (
    <div>
      <h1>My Task List</h1>
      <form action={addTask}>
        <input type="text" name="task" placeholder="New task" required />
        <button type="submit">Add Task</button>
      </form>
      <p>Task list will refresh after adding!</p>
    </div>
  );
}

Granular Control with `revalidateTag`

Sometimes you need more granular control over caching than just revalidating an entire path. This is where revalidateTag comes in.

When fetching data, you can assign a custom tag using the fetch API. Then, after a mutation, you can use revalidateTag('my-data-tag') to invalidate only the data associated with that specific tag.

When to use `revalidateTag`

Use revalidateTag when:

  • Data is fetched from an external API using fetch.
  • The data is shared across multiple pages or components.
  • You want to update specific data without re-rendering entire pages.

It's ideal for scenarios like updating a single user's profile data that might appear on various pages.

Post-Mutation Redirection

After a successful data mutation, you often want to redirect the user to another page (e.g., a success page or the updated list page). Next.js provides a redirect helper for this.

You can use redirect('/dashboard') inside your Server Action to send the user to the dashboard after a form submission.

Full Flow: Mutate, Revalidate, Redirect

This example combines all concepts: a form submission triggers a Server Action, which mutates data, revalidates the relevant path, and then redirects the user to a confirmation page.

import { revalidatePath, redirect } from 'next/cache';

async function createPost(formData) {
  'use server';
  const title = formData.get('title');
  const content = formData.get('content');

  // Simulate saving new post to a DB
  console.log('New Post:', { title, content });
  await new Promise(r => setTimeout(r, 700));

  revalidatePath('/posts'); // Revalidate the posts list page
  redirect('/posts/success'); // Redirect to a success page
}

export default function NewPostPage() {
  return (
    <div>
      <h1>Create New Post</h1>
      <form action={createPost}>
        <input type="text" name="title" placeholder="Title" required />
        <textarea name="content" placeholder="Content" required />
        <button type="submit">Publish Post</button>
      </form>
    </div>
  );
}

Quick Check on Revalidation

A Server Action successfully creates a new product and you want to update the product listing page (/products) and also ensure any cached data specifically tagged 'featured-products' is refreshed. Which revalidation methods should you use?

Recap: Mutate & Revalidate

Great job! You've learned how Server Actions are key to mutating data on the server. You also mastered how to keep your UI fresh:

  • Use Server Actions for creating, updating, or deleting data.
  • Employ revalidatePath to refresh data for specific routes.
  • Utilize revalidateTag for fine-grained cache invalidation of tagged fetch requests.
  • Use redirect to guide users after a successful action.

This powerful combination ensures your Next.js applications are always showing accurate, up-to-date information.

Frequently asked questions

Is the “Mutating Data & Revalidation” lesson free?

Yes — the full text of “Mutating Data & Revalidation” 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 “Mutating Data & Revalidation”?

Learn how Server Actions can mutate data on the server and automatically revalidate cached data to update the UI. 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 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Mutating Data & Revalidation” 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

  1. Basic Server Action Forms
  2. Mutating Data & Revalidation
  3. Error Handling in Actions
  4. Optimistic UI and Pending States with Server Actions
← Back to Next.js 15 Fullstack (App Router + Server Actions)