feat: mutation based cache invalidation in `proxy-cache`

[shreemaan-abhishek]

Description

created on behalf of a slack member

Hi everyone, I have a question regarding the proxy-cache plugin. Is there a smart way to invalidate the cache after an entity update? For example I have a post entity that is in the cache. After I update the post’s description. I expect other users to get the newly updated description. I read the docs and I am not clear on how to invalidate cache in a smart way. In some Graphql CDNs this is possible through the use of mutation based cache invalidation. I am wondering how to achieve something similar programmatically. if possible, can the single post we have updated, also be updated in a cached list of posts ?

Thanks to: Ian C

[kayx23]

https://apisix.apache.org/docs/apisix/plugins/proxy-cache/

[naina24]

I have deployed apisix on openshift and trying to use proxy-cache for the routes but it is not working as cache is not getting generated.

[github-actions[bot]]

This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.