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
I understand this is a feature request and questions should be posted in the Community Forum
I searched issues and couldn’t find anything (or linked relevant results below)
Problem
When I was talking to dev ops about companion deployment, they would have liked it to support redis sentinel natively, which apparently currently is not the case.
Solution
I'm no expert on this topic, but afaict ioredis has sophisticated support for this, while node-redis does not.
When I saw connect-redis abstracts them away, I was thinking it would be super straightforward to switch from node-redis to ioredis - it was until it wasn't
Porting createClient was easy, redis-emitter not sooo much.
I'm not sending a PR because switching libraries is usually rather controversial and I would like to discuss options first.
Have you considered switching to ioredis or are there reasons not to do it?
Possibly a breaking change if someone is passing advanced options to the library...
Alternatives
switch to ioredis completely
support ioredis and node-redis simultaneously
don't change anything (just updateredis-connect which is slightly outdated)
Personally I've used ioredis in other projects and have been very happy with it, but yea porting redis-emitter might be non trivial, so I'm not sure if this is something that will be prioritised any time soon.
I'm not against this change but I would be curious what the cons are of migrating. Is it breaking for custom providers? Is there functionality node-redis has which ioredis doesn't have?
Initial checklist
Problem
When I was talking to dev ops about companion deployment, they would have liked it to support redis sentinel natively, which apparently currently is not the case.
Solution
I'm no expert on this topic, but afaict ioredis has sophisticated support for this, while node-redis does not.
When I saw
connect-redis
abstracts them away, I was thinking it would be super straightforward to switch fromnode-redis
toioredis
- it was until it wasn'tPorting
createClient
was easy,redis-emitter
not sooo much.I'm not sending a PR because switching libraries is usually rather controversial and I would like to discuss options first.
Have you considered switching to
ioredis
or are there reasons not to do it?Possibly a breaking change if someone is passing advanced options to the library...
Alternatives
ioredis
completelyioredis
andnode-redis
simultaneouslyredis-connect
which is slightly outdated)Excerpt from my patch
The text was updated successfully, but these errors were encountered: