Create Redis session backend

[bradleybeddoes]

We currently have an in memory session backend which is very useful for proving out basic use cases and initial deployments but isn't suitable for larger deployments i.e. with multiple containers that we're treating like :cow2:.

Create a second reference implementation (standalone crate) that utilises Redis (and hence services such as elasticache) as a session Backend .

It would be a good idea to reach out to @benashford to find out the status of https://github.com/benashford/redis-async-rs noting no recent commits. There is another crate in a similar state with no recent commits at https://github.com/tokio-rs/tokio-redis which would also be worth finding out status on.

A non Tokio integrated, but well maintained crate exists at https://github.com/mitsuhiko/redis-rs

[benashford]

Regarding redis-async-rs, it's still currently active, there's a feature branch where most of the recent commits have been going, but due to other time pressures it's going to be a very slow moving project.

Of course, you're more than welcome to give it a try and see if it fits your needs, but it is way short of the level of features (and testing) that redis-rs has at this stage.

[bradleybeddoes]

Thanks for the info @benashford will poke around your feature branch when I have some time.

[Marwes]

For https://github.com/mitsuhiko/redis-rs I made a pair of PRs to add async support for it. It is still in queue while I finish a release for the parser dependendcy that they need but that should be done in ~2 weeks.

https://github.com/mitsuhiko/redis-rs/pull/141 https://github.com/mitsuhiko/redis-rs/pull/143

[bradleybeddoes]

@Marwes this is fantastic. Could you keep us updated on progress by chance?

Once this is merged trying it out with Gotham would be an interesting exercise.