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
It is a convention to prefix your keys with some kind of namespace to help sort through them. However.. if you want a namespace across your whole application transparently.. that would be a bit more work.
There is a ruby implementation of this Here.
Along with a node clone Here.
Would this be something to be considered being added into the library? I know node's philosophy for packages is to make them small and concentrate on one thing and do it well. This may be breaking that idea to some purists but to many who are dealing with multi tenant redis usage this may help simplify things significantly!
As always this should be an opt-in feature. Maybe adopt something similar to the ruby version where the existing var redis = new Redis(); could be passed to something like var namespaceRedis = new RedisNamespace(redis, 'Appname');
The text was updated successfully, but these errors were encountered:
This was something new to me that I came across..
It is a convention to prefix your keys with some kind of namespace to help sort through them. However.. if you want a namespace across your whole application transparently.. that would be a bit more work.
There is a ruby implementation of this Here.
Along with a node clone Here.
Would this be something to be considered being added into the library? I know node's philosophy for packages is to make them small and concentrate on one thing and do it well. This may be breaking that idea to some purists but to many who are dealing with multi tenant redis usage this may help simplify things significantly!
As always this should be an opt-in feature. Maybe adopt something similar to the ruby version where the existing
var redis = new Redis();
could be passed to something likevar namespaceRedis = new RedisNamespace(redis, 'Appname');
The text was updated successfully, but these errors were encountered: