[FEATURE] Using KV for caching is a bit expensive. Could we add a solution that uses D1?

[j4tmr]

Is your feature request related to a problem?

Using KV for caching is a bit expensive. Could we add a solution that uses D1 instead, or perhaps implement a more complex configuration option? For example, selecting where the cache should be stored based on its tag.

Describe the solution you'd like

Describe alternatives you've considered

@opennextjs/cloudflare version

0.5.3

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)

[james-elicx]

Thanks for the issue.

We're going to look at adding an R2 option for the incremental cache.

D1 is an interesting one as there's a row size limit of 2mb, much lower than KV's 25mb limit for values, and so i can imagine that there potentially might be apps that have insanely large pages that could exceed that limit.

Having said that though, it will likely be added as an option at some point. My view is that we should support many different options, and leave it up to the users to decide which storage mechanism best works for their use case.

[vicb]

We have added more option for caching, see https://opennext.js.org/cloudflare/caching

R2 would be less expensive and you can also use regional cache to lower the cost