I am Derrick, a Support Engineering Manager at Strapi and also one of the co-maintainers of this plugin. With the release of Strapi 5 I will be working with @stafyniaksacha and @Boegie19 to do some heavy rewrites to this plugin to update it to Strapi 5. There almost certainly will be some breaking changes but with that will ideally bring some new features hopefully.
Below are some things I would like to tackle during the rewrite, albeit we don't know how long this rewrite is going to take. Regardless I'll detail some of my thoughts below but would also like to hear yours.
[ ] Completely refactor the way we inject the caching middlewares
The way these were injected in the current version was more of a hack than anything and in certain situtations would completely break any custom middlewares the user added for additional security since it would bypass them
Ideally the goal would be to work with the Strapi team (not me lol but our engineering team proper) to have a natively supported way to do this properly
[ ] Allow for more detailed configuration on when and how the cache is busted especially for relations, components, ect
[ ] Possibly (maybe) allow for a way to do caching for authenticated requests
How this will be done is still up for some debate but ideally we could allow for caching by specific user, role, ect
[ ] More advanced Admin Panel integrations possibly including a "cache view" to see what data is cached, how long it's TTL is, and when/how long til that TTL expires
[ ] Better debugging and maybe even a "cache bust log" (possibly saved to the database, TBD)
[ ] Rename this package to fit more in-line with the way we would like to see the community org go
Hello all o/
I am Derrick, a Support Engineering Manager at Strapi and also one of the co-maintainers of this plugin. With the release of Strapi 5 I will be working with @stafyniaksacha and @Boegie19 to do some heavy rewrites to this plugin to update it to Strapi 5. There almost certainly will be some breaking changes but with that will ideally bring some new features hopefully.
Below are some things I would like to tackle during the rewrite, albeit we don't know how long this rewrite is going to take. Regardless I'll detail some of my thoughts below but would also like to hear yours.
[ ] Rename this package to fit more in-line with the way we would like to see the community org go
strapi-plugin-rest-cache
->@strapi-community/plugin-rest-cache
strapi-provider-rest-cache-couchbase
->@strapi-community/provider-rest-cache-couchbase
strapi-provider-rest-cache-memory
->@strapi-community/provider-rest-cache-memory
strapi-provider-rest-cache-redis
->@strapi-community/provider-rest-cache-redis
And I think that's about all I had in mind so far but I'm open to hearing more community suggestions