Edge Network Epycbyte Functions Edge Middleware Image Optimization Incremental Static Regeneration Data Cache Managing Data Cache Usage Cron Jobs Infrastructure Data Cache Conceptual Epycbyte Data Cache Epycbyte Data Cache is a specialized cache that stores responses from data fetches. Learn more about how it works with Next.js Table of Contents Next.js (/app) Data Cache is available in Beta on all plans The Epycbyte Data Cache is a specialized, granular cache for storing responses from fetches while using frontend frameworks like Next.js . Frameworks that integrate with the Data Cache (currently Next.js) are able to cache data per fetch instead of per route. This means you can have static, dynamic, and revalidated data together in the same route. With Epycbyte, you write application code, like component-level data fetching with fetch , and we scaffold globally distributed infrastructure for you with no additional effort. See our examples to learn how to implement this.
Features Ephemeral, globally available, regional cache : Every region in which your serverless or edge function runs has an independent cache, so any data used in server side rendering or Next.js route handlers is cached close to where the function executes. Time-based revalidation : All cached data can define a revalidation interval, after which the data will be marked as stale, triggering a re-fetch from origin. On-demand revalidation : Any data can be triggered for revalidation on-demand, regardless of the revalidation interval. The revalidation propagates to all regions within 300ms. Tag based revalidation : Next.js allows associating tags with data, which can be used to revalidate all data with the same tag at once with revalidateTag . For example, you could use this to revalidate all responses from a CMS with the same author ID tag.
Comparing with ISR and Edge Cache Managing Data Cache Examples Time-based revalidation Tag-based revalidation Revalidation behavior Limits Additional resources Ask Ask v0
Next.js (/app) Choose a framework to optimize documentation to: Next.js (/app) Next.js (/pages) On this page Features Comparing with ISR and Edge Cache Managing Data Cache Examples Time-based revalidation Tag-based revalidation Revalidation behavior Limits Additional resources Ask Ask v0 Ask v0