AI BriefingVercel consolidates Data Cache into Runtime Cache for unified data caching
·2026.10.30 09:00
Key point
Existing Next.js fetch caching and unstable_cache code remains unchanged, while Pro and Enterprise projects receive 8x and 10x larger storage allocations respectively.
Details
- Vercel integrates Data Cache into Runtime Cache, providing a single product for data caching across frameworks and APIs without requiring code changes for Next.js users.
- Circuit breakers for tag store freshness checks reduced p99 cache-service read latency to about one-fifth of its previous level during heavy traffic bursts in the largest region.
- Storage budgets increased for Pro projects (8x previous Data Cache pool) and Enterprise projects (10x previous Data Cache storage), halving cache miss rates for Enterprise projects with frequent evictions.
- The distributed service handles over 440 million reads and moves more than 18 TB of data hourly, using Redis fleets in every Vercel region with regional isolation and shared tag infrastructure for invalidation.
- New observability features include deployment markers, revalidation causes, and write utilization to help identify data written but rarely read.
- Previously unbilled Data Cache reads and writes now follow Runtime Cache pricing, with existing teams receiving migration details in advance.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.