runtime-cache

Regional key-value caching in Vercel serverless applications stores computed data close to the request location, reducing repeated computation and database load without building a custom cache layer. This approach applies runtime cache strategies for faster serverless responses.

Tag-based invalidation for Next.js API caching expires related entries together when content changes, such as after CMS updates or webhook events. It groups cached responses by tags, allowing targeted purges instead of clearing entire caches.

You can coordinate Vercel Runtime Cache with Next.js cache components and CDN purge functions to apply distinct cache layers without conflicts. This ensures regional storage, framework caching, and CDN purge operations remain separated and managed correctly.

Runtime-cache supports TTL-based expiry for automatic time-outs and namespace configuration for isolating cached data. These features satisfy requirements for observability and framework-agnostic deployment across serverless applications.

The best way to cache API responses per region is using Vercel Runtime Cache strategies for regional key-value storage. You can then invalidate all related entries together through tag-based invalidation when the product catalog changes.