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

Tag-Based Invalidation for Granular Cache Busting

Attach cache tags to fetches and invalidate exactly the affected data after mutations.

Tag-Based Invalidation for Granular Cache Busting 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.

Why Tag-Based Invalidation

In Next.js 15, the Data Cache persists fetch results across requests and deployments. The challenge is busting exactly the right entries after a mutation.

  • Time-based revalidation (revalidate: 60) is coarse and clock-driven.
  • Path-based (revalidatePath) clears whole route segments.
  • Tag-based lets you label individual fetches and invalidate just those, no matter which page rendered them.

Tags give you granular, surgical cache busting: update one product, invalidate only the fetches that read that product.

Attaching a Tag to a Fetch

You attach tags through the next.tags option on the extended fetch. Each tag is a plain string you choose.

Here a product list fetch is labelled with two tags: a broad products tag and a specific product-42 tag.

  • The broad tag invalidates the whole collection.
  • The specific tag invalidates one item.
async function getProduct(id: string) {
  const res = await fetch(`https://api.shop.com/products/${id}`, {
    next: { tags: ['products', `product-${id}`] },
  });
  if (!res.ok) throw new Error('Failed to load product');
  return res.json();
}

Invalidating with revalidateTag

After a mutation, call revalidateTag(tag) from next/cache. Every cached fetch carrying that tag is marked stale; the next request re-fetches fresh data.

This runs inside a Server Action or a Route Handler — server-only contexts where mutations happen.

  • revalidateTag does not return a promise you await for re-fetching; it just marks entries stale.
  • Multiple tags? Call it once per tag.
'use server';
import { revalidateTag } from 'next/cache';

export async function updateProduct(id: string, data: FormData) {
  await fetch(`https://api.shop.com/products/${id}`, {
    method: 'PATCH',
    body: JSON.stringify({ name: data.get('name') }),
  });
  // Bust only this product's cached reads
  revalidateTag(`product-${id}`);
}

Broad vs Narrow Tags

Design a small tag hierarchy so you can choose the right blast radius:

  • products — invalidate the whole catalog (e.g. after a bulk import).
  • product-42 — invalidate a single item (e.g. an edit).
  • product-42-reviews — invalidate a related slice without touching the product itself.

Rule of thumb: tag each fetch with both a collection tag and an entity tag. Then mutations can pick the smallest tag that covers the change.

Tagging Reads Across Pages

A tag is global to the Data Cache, not tied to a route. If the home page and the detail page both fetch product-42 with the same tag, one revalidateTag('product-42') busts both.

This is the key advantage over revalidatePath: you don't have to know which pages consumed the data.

// app/page.tsx (home) and app/products/[id]/page.tsx both call this
export async function getProductSummary(id: string) {
  const res = await fetch(`https://api.shop.com/products/${id}`, {
    next: { tags: [`product-${id}`] },
  });
  return res.json();
}

unstable_cache for Non-fetch Data

Not all data comes from fetch — direct DB queries (Prisma, Drizzle) bypass the Data Cache. Wrap them with unstable_cache to gain tag support.

The third argument takes tags and revalidate. The same revalidateTag call busts these entries too.

import { unstable_cache } from 'next/cache';
import { db } from '@/lib/db';

export const getCachedUser = unstable_cache(
  async (id: string) => db.user.findUnique({ where: { id } }),
  ['user-by-id'],
  { tags: ['users'], revalidate: 3600 },
);

Dynamic Tags in unstable_cache

The cache key parts (second arg) must be static enough to identify the function, but you often want a per-entity tag. Build the tag from the argument and pass it in the options.

Return the function so each call gets the right entity tag, enabling revalidateTag('user-7') precision.

import { unstable_cache } from 'next/cache';
import { db } from '@/lib/db';

export function getCachedUser(id: string) {
  return unstable_cache(
    async () => db.user.findUnique({ where: { id } }),
    ['user', id],
    { tags: [`user-${id}`, 'users'] },
  )();
}

Building Tag Names Safely

Inconsistent tag strings silently fail — a mismatched tag busts nothing. Centralize tag construction in pure helper functions so reads and writes always agree.

This is standalone, idiomatic TypeScript: the helpers produce the exact same strings used in both next.tags and revalidateTag.

const tags = {
  products: () => 'products',
  product: (id: string) => `product-${id}`,
  productReviews: (id: string) => `product-${id}-reviews`,
};

console.log(tags.products());
console.log(tags.product('42'));
console.log(tags.productReviews('42'));

Invalidating Multiple Tags Atomically

One mutation often affects several cached slices. After updating a product you may need to bust the item, the collection listing, and the search index.

Call revalidateTag for each. They all take effect together before the action's response returns to the client.

  • Order doesn't matter — all are marked stale.
  • Keep the set minimal to avoid over-fetching elsewhere.
'use server';
import { revalidateTag } from 'next/cache';

export async function publishProduct(id: string) {
  await fetch(`https://api.shop.com/products/${id}/publish`, { method: 'POST' });
  revalidateTag(`product-${id}`);
  revalidateTag('products');
  revalidateTag('search-index');
}

Tag vs Path: Choosing

Both revalidateTag and revalidatePath exist for different jobs:

  • Use tags when the same data appears on many routes, or when you only want to bust data (not the rendered route cache assumptions of a layout).
  • Use path when an entire route's output changed and you don't track tags there.

They compose: a Server Action can call both. Prefer tags for data, paths for whole-page structural changes.

End-to-End in a Server Action

Here is the full loop: a form posts to a Server Action, the action mutates the backend, then invalidates the precise tags. The next render of any page reading those tags gets fresh data automatically.

Note we bust both the entity tag and the collection tag because the edit changes the listing too.

'use server';
import { revalidateTag } from 'next/cache';
import { redirect } from 'next/navigation';

export async function editProduct(id: string, formData: FormData) {
  await fetch(`https://api.shop.com/products/${id}`, {
    method: 'PATCH',
    body: JSON.stringify({ name: formData.get('name') }),
    headers: { 'Content-Type': 'application/json' },
  });
  revalidateTag(`product-${id}`);
  revalidateTag('products');
  redirect(`/products/${id}`);
}

Quick Check

A product detail fetch is tagged ['products', 'product-42'] and is also shown on the home page list (same tag). You edit only product 42's name. What is the most precise way to refresh both views without over-invalidating other products?

Recap

You learned granular, tag-based cache busting in Next.js 15:

  • Attach tags via next: { tags: [...] } on fetch, and via the tags option of unstable_cache for non-fetch data.
  • Use a collection tag plus a per-entity tag so mutations pick the smallest blast radius.
  • Call revalidateTag(tag) inside Server Actions or Route Handlers — once per tag, atomically.
  • Tags are global: one call refreshes the data on every route that read it, unlike revalidatePath.
  • Centralize tag strings in helpers so reads and writes never drift apart.

Frequently asked questions

Is the “Tag-Based Invalidation for Granular Cache Busting” lesson free?

Yes — the full text of “Tag-Based Invalidation for Granular Cache Busting” 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 “Tag-Based Invalidation for Granular Cache Busting”?

Attach cache tags to fetches and invalidate exactly the affected data after mutations. 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 “Tag-Based Invalidation for Granular Cache Busting” 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. The Four Caches: Request, Data, Full Route, and Router
  2. Time-Based and On-Demand Revalidation Strategies
  3. Tag-Based Invalidation for Granular Cache Busting
  4. Opting Out: Dynamic Rendering and no-store
← Back to Next.js 15 Fullstack (App Router + Server Actions)