Simplifying runtime caching on Vercel

Vercel is consolidating its Data Cache service into Runtime Cache to provide a single caching platform across Next.js, other frameworks, and direct APIs, while maintaining compatibility for existing Next.js fetch caching and unstable_cache users. Runtime Cache stores application data rather than complete HTTP responses, operates regionally through Redis-backed infrastructure, and supports tag-based invalidation that propagates globally within milliseconds. The service processes more than 440 million reads and 18 TB of data per hour, and recent improvements include circuit breakers that reduce read latency during traffic spikes, larger storage allocations for Pro and Enterprise projects, and enhanced observability for cache usage, revalidation, deployments, and write efficiency. The migration unifies fetch caching, unstable_cache, getCache, and use cache: remote under shared storage budgets and tools, increases storage capacity substantially, and shifts previously unbilled Data Cache operations to Runtime Cache pricing, with rollout and billing details provided to existing customers in advance.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.