Simplifying runtime caching on Vercel

This post announces the consolidation of Vercel's Data Cache into the Runtime Cache product. Previously, Next.js fetch caching and unstable_cache used Data Cache, while getCache and 'use cache: remote' used Runtime Cache. The migration brings all four APIs under the unified Runtime Cache, simplifying usage and management. This change includes increased storage allocations for Pro (8x previous) and Enterprise (10x previous) projects. Previously unbilled Data Cache reads/writes will now follow Runtime Cache pricing. The post also details improvements to Runtime Cache: circuit breakers for faster reads during traffic bursts (reducing p99 cache-service read latency by ~1/5th), increased storage budgets leading to halved cache miss rates for some Enterprise projects, and enhanced observability with deployment markers, revalidation causes, and write utilization.