You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/03/21 10:25:52 UTC
[GitHub] [apisix] fatihbm opened a new issue #6676: feat: Redis backend support for cache_strategy in proxy-cache plugin.
fatihbm opened a new issue #6676:
URL: https://github.com/apache/apisix/issues/6676
### Description
Hi,
I have wondered, is there any particular reason why the proxy-cache plugin doesn't have redis backend support for cache_strategy?
If it had been this support, it could provide distributed cache support and give the object's validity more accurately without node dependency.
Currently, the validity of the content to be cached is determined only when a request is made to the relevant apisix node independent of other nodes.
Therefore, each node is responsible for its own cache time. So that causes problems when caching highly variable objects under high traffic. For example, one user can have an older version, and another can have a newer version even if they requested it at the same time.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] jagerzhang commented on issue #6676: feat: Redis backend support for cache_strategy in proxy-cache plugin.
Posted by GitBox <gi...@apache.org>.
jagerzhang commented on issue #6676:
URL: https://github.com/apache/apisix/issues/6676#issuecomment-1075961866
agree
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix] tzssangglass commented on issue #6676: feat: Redis backend support for cache_strategy in proxy-cache plugin.
Posted by GitBox <gi...@apache.org>.
tzssangglass commented on issue #6676:
URL: https://github.com/apache/apisix/issues/6676#issuecomment-1076216675
When adding redis as a cache, do we need to force the cached data to be fetched from redis? In that case, there will be a performance loss.
> Therefore, each node is responsible for its own cache time. So that causes problems when caching highly variable objects under high traffic. For example, one user can have an older version, and another can have a newer version even if they requested it at the same time.
This problem does exist, but is it not a very serious problem for proxy cache scenarios?
I think that proxy caching allows cached data and upstream response data to be inconsistent within the cache time, which is something that will be considered at the beginning of the proxy cache design.
Anyway, using redis as the cache implementation for proxy cache provides more options.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org