Did anyone try using custom cache handler (via incremental cache handler path) in pages router?

[mskwon1]

Summary

Hi I am trying to solve shared isr storage problem between multiple next js web server instances (in aws environment)

first I tried using efs but couldn't really make it to work :(

and then I looked at custom cache handler in app router docs, although there aren't any sufficient documents, I tried redis custom cache handler and it is working like a charm.

But I am worried about using this custom cache handler in pages router since it is still an exprimental option and nothing really is stated in the pages router documents. So.. is anyone using custom cache handler in pages router and had some kind of issues?

Additional information

No response

Example

No response

[better-salmon]

Hi, @mskwon1! Check out the @neshca/cache-handler library. It supports both the App and the Pages router. And it simplifies custom configurations as well.

It is not a silver bullet, but I hope it will help you.

[JannikZed]

very old discussion! But I want to point out now our redis cache handler, that supports also Next.js 16 with app / pages router and full cache components support: https://github.com/trieb-work/nextjs-turbo-redis-cache