refactor(deps): replace redis with valkey #17

New issue

Closed

opened 2025-07-24 07:19:14 +00:00 by chartgerink · 1 comment

chartgerink commented

2025-07-24 07:19:14 +00:00

Owner

We want to use boring dependencies so that we can focus on the exciting things we do with it. This allows us to create RE as a reliable service.

Valkey is a fork of Redis, which is hosted by the Linux Foundation. This provides more trust in the software remaining open source in the future, and making it more boring. However, upon trying to implement this (as of July 24th, 2025), there is no stable Rust driver for valkey.

As a result, we implement redis and open this issue to track the work on valkey. If at all possible, we will seek to swap out redis with valkey before release. This does require a stable valkey driver (currently only alpha versions exist; valkey = "0.0.0-alpha5").

On a related note, we need to consider that Open Telekom Cloud, which we will use for our production deployments, provides redis as a service, but not valkey as a service. Hence, we will need to deploy + manage this ourselves.

Redis changed their license multiple times over the past few years, becoming more restrictive and reverting after lots of pushback. Regardless of the current licensing state, it indicates uncertainty in this domain. We want to use boring dependencies so that we can focus on the exciting things we do with it. This allows us to create RE as a reliable service. Valkey is a fork of Redis, which is hosted by the Linux Foundation. This provides more trust in the software remaining open source in the future, and making it more boring. However, upon trying to implement this (as of July 24th, 2025), there is no stable Rust driver for valkey. As a result, we implement redis and open this issue to track the work on valkey. If at all possible, we will seek to swap out redis with valkey before release. This does require a stable valkey driver (currently only alpha versions exist; `valkey = "0.0.0-alpha5"`). --- On a related note, we need to consider that Open Telekom Cloud, which we will use for our production deployments, provides redis as a service, but not valkey as a service. Hence, we will need to deploy + manage this ourselves.