Skip to content
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

[FEATURE] Support Cloudflare Cache API as alternative to KV #134

Open
2 tasks done
nathanclevenger opened this issue Nov 14, 2024 · 0 comments · May be fixed by #136
Open
2 tasks done

[FEATURE] Support Cloudflare Cache API as alternative to KV #134

nathanclevenger opened this issue Nov 14, 2024 · 0 comments · May be fixed by #136
Labels
enhancement New feature or request

Comments

@nathanclevenger
Copy link

Is your feature request related to a problem?

Currently @opennextjs/cloudflare uses Workers KV as the cache for your Next.js app.

Some of our use cases have very high volumes of requests that we would like to cache, but it's not at all cost effective to Write/Read constantly to KV.

Describe the solution you'd like

For these use cases, we don't need global-distributed cache, as local colo-specific cache is fine, so we would simply prefer if we could configure the Next Cache to use the Cloudflare Workers Cache API.

Describe alternatives you've considered

As mentioned, it appears the only 2 alternatives today are to either disable caching or use KV for Next caching - We would just really appreciate an option to use the Cloudflare Cache API

@opennextjs/cloudflare version

0.2.1

Additional context

No response

Before submitting

  • I have checked that there isn't already a similar feature request
  • This is a single feature (not multiple features in one request)
@nathanclevenger nathanclevenger added enhancement New feature or request triage labels Nov 14, 2024
@vicb vicb removed the triage label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants