Hello,
I have a question regarding Vercel’s caching scope.
“When a revalidation is triggered, the path or cache tag is marked stale globally in every Vercel Edge Network region. The next request to that path or tag, in any region, will trigger a revalidation and update the cache globally. The regional cache in all regions is purged and updated within 300ms.”
From my understanding, with regular ISR, the updated page is cached only on the edge nodes that have served user requests for that page, whereas with on-demand ISR, the updated page is propagated across all edge nodes globally.
“With regular ISR, the updated page is cached only at the edge nodes which have handled user requests for the page. On-demand ISR regenerates and redistributes the page across the edge network so that users worldwide will automatically see the most recent version of the page from the edge cache without seeing stale content. We also avoid unnecessary regenerations and serverless function calls, reducing operational costs compared to regular ISR.” - Introduction
Does the behavior described above also apply to time-based revalidations (not using revalidatePath or revalidateTag, but just revalidate)?