Skip to content

Support for Cache Invalidation by Tag #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Gwemox opened this issue Oct 11, 2024 · 1 comment
Closed

Support for Cache Invalidation by Tag #91

Gwemox opened this issue Oct 11, 2024 · 1 comment
Labels
enhancement New feature or request planned

Comments

@Gwemox
Copy link

Gwemox commented Oct 11, 2024

Description

It appears that @opennextjs/cloudflare does not support cache invalidation by tag. Currently, fetch places cache data in a Cloudflare KV store (NEXT_CACHE_WORKERS_KV). However, calling tag-based invalidation through @next/cache does not seem to work as expected.

Context and Need

In environments with frequently updated or dynamic content, precise cache control is essential. Using tag-based cache invalidation would allow for targeted, granular cache management, reducing the need for global purges and improving overall performance.

Request

Please add support for cache invalidation by tag.

Expected Benefits

  • Improved performance by avoiding full cache purges.
  • Granular control over cached content for end-users.
  • Enhanced cache management for dynamic content projects with frequent updates.

Thank you for considering this enhancement! I’d be happy to provide additional information or discuss this feature in detail.

@vicb
Copy link
Contributor

vicb commented Jan 16, 2025

Will be adressed by #105

@vicb vicb closed this as completed Jan 16, 2025
@github-project-automation github-project-automation bot moved this from P1 - need to be addressed to Done in `@opennextjs/cloudflare` prioritization and tracking Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request planned
Development

No branches or pull requests

2 participants