What problem does it solve?
Provides clear, actionable guidance for implementing a per-region ephemeral key-value cache on Vercel, enabling teams to reduce origin load and control cache invalidation without relying on persistent TCP-backed stores.
Core Features & Use Cases
- Regional KV store guidance: Explains how the Runtime Cache works across Functions, Routing Middleware, and Builds, and when to prefer it over framework-level or CDN caching.
- Tag-based invalidation: Shows how to attach tags to cached items and expire them safely to propagate invalidation with minimal staleness.
- Integration & migration advice: Covers Next.js cache directives, CLI purge commands, observability points, and migration paths from direct Redis clients to Upstash or Vercel Storage for serverless compatibility.
- Use Case: Reduce database reads for frequently requested API data by storing compute results with TTL and tags, then expiring related entries on content updates.
Quick Start
Add regional Runtime Cache reads and writes to your function and tag responses so you can expire related entries after a content update.