Skip to content

Redis Adapter #396

@Totodore

Description

@Totodore

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.

Metadata

Metadata

Assignees

Labels

A-redis-adapterArea related to redis-adapterC-EnhancementRelated to an enhancementE-HardCall for participation: Experience needed to fix: Hard / a lotP-HighHigh priority

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions