-
-
Notifications
You must be signed in to change notification settings - Fork 70
Labels
A-redis-adapterArea related to redis-adapterArea related to redis-adapterC-EnhancementRelated to an enhancementRelated to an enhancementE-HardCall for participation: Experience needed to fix: Hard / a lotCall for participation: Experience needed to fix: Hard / a lotP-HighHigh priorityHigh priority
Description
This is a tracking issue for a redis adapter. Once the async adapter PR is merged (see #395) it will be possible to start working on a redis adapter. First thought are:
We must let the end user choose its Redis client implementation. There are currently multiple potential candidates:
The best way to implement that would be to make a simple compat trait for every redis feature the adapter use (mostly PUB/SUB AFAIK). We could then put each redis implementation behind a feature flag for the most used implementation and otherwise propose the user to implement manually the compat trait if he wants another Redis flavour.
musjj
Metadata
Metadata
Assignees
Labels
A-redis-adapterArea related to redis-adapterArea related to redis-adapterC-EnhancementRelated to an enhancementRelated to an enhancementE-HardCall for participation: Experience needed to fix: Hard / a lotCall for participation: Experience needed to fix: Hard / a lotP-HighHigh priorityHigh priority
Projects
Status
Done