Closed noahprince22 closed 6 years ago
If multiple services on the same cluster use the same redis client with feathers-sync, there's a possibility for collisions. This will only happen if the services have the same name, but it's still something to be concerned about.
If I get time I'll do a PR to fix it, should probably just need to add an option like prefix for redis, and change https://github.com/feathersjs-ecosystem/feathers-sync/blob/6c3f14a2bbc9e8d67f038e2a761fd80e831ff55a/src/redis.js#L18
prefix
For now we're just using AMQP for one service and Redis for the other, since we have both.
In the next version, only one Redis key is being subscribed to and you can set it in the options to avoid name clashes.
If multiple services on the same cluster use the same redis client with feathers-sync, there's a possibility for collisions. This will only happen if the services have the same name, but it's still something to be concerned about.
If I get time I'll do a PR to fix it, should probably just need to add an option like
prefix
for redis, and change https://github.com/feathersjs-ecosystem/feathers-sync/blob/6c3f14a2bbc9e8d67f038e2a761fd80e831ff55a/src/redis.js#L18For now we're just using AMQP for one service and Redis for the other, since we have both.