You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use redis.UniversalClient to abstract any redis configuration our services may use, from one instance only to sentinel and redis-cluster. It works fine, however, we need to also enable and stress test our services under different circumstances, so we would like to offer a Noop variant of our caching layer and see how our service react. It is possible for us to handle that entirely, however, we realized that if redis-go offered some sort of NoopClient then we could benefit from it, and that makes our code and wrappers around redis-go more robust, as they will run except for the underlying low level client, which will act as a 0% hit rate cache.
Has anyone tried to achieve something similar?
PS: we created our own interface that is a subset of redis.UniversalClient, and we impl noop for the methods we care. But this is far from ideal as if redis-go change it may break it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We use
redis.UniversalClient
to abstract any redis configuration our services may use, from one instance only to sentinel and redis-cluster. It works fine, however, we need to also enable and stress test our services under different circumstances, so we would like to offer a Noop variant of our caching layer and see how our service react. It is possible for us to handle that entirely, however, we realized that if redis-go offered some sort ofNoopClient
then we could benefit from it, and that makes our code and wrappers around redis-go more robust, as they will run except for the underlying low level client, which will act as a 0% hit rate cache.Has anyone tried to achieve something similar?
PS: we created our own interface that is a subset of redis.UniversalClient, and we impl noop for the methods we care. But this is far from ideal as if redis-go change it may break it.
Beta Was this translation helpful? Give feedback.
All reactions