From the source
Vercel is folding its Data Cache into Runtime Cache so developers have one data caching product across frameworks and APIs, with no code changes for Next.js fetch caching or unstable_cache users.
- Data Cache had been Vercel's caching service for the Next.js App Router, while getCache and 'use cache: remote' used Runtime Cache; the migration brings all four APIs under one set of storage budgets and usage tools.
- On Pro, each project and environment now gets its own storage allocation, 8x the space of Data Cache's previous team-wide pool, and Enterprise projects get 10x their previous Data Cache storage.
- Vercel says the infrastructure handles more than 440 million reads and moves more than 18 TB of data every hour, with each region keeping its own cache and a cache hit taking one round trip.
- Circuit breakers enabled in every region in August let reads fall back to in-memory tag timestamps during traffic bursts, and Vercel says p99 cache-service read latency in its largest region fell to about one fifth of its previous level at comparable traffic.
- Previously unbilled Data Cache reads and writes will follow Runtime Cache pricing, new teams use Runtime Cache automatically, and existing teams will get migration and billing details in advance.
