Redis replacement - Help with KeyDB

Project Discussion
1

Unfortunately, redis has relicensed and is no longer open source and therefore no longer license-compatible with Fedora. There are a number of redis users in EPEL and Fedora, myself included, that are going to be impacted by this, as we cannot ship any future versions of redis moving forward.

Luckily, there are a couple of options for redis alternatives, such as KeyDB from SnapChat and a very young GPL relicensed fork called redict.

Of the two, KeyDB is the more mature project and is currently in package review for inclusion in Fedora and RHEL. That still leaves the question of what to do with existing Redis-7 deployments on Fedora, though, as currently KeyDB is compatible to v6, which is conveniently where EPEL currently targets.

KeyDB is open to rebasing to v7, but their current maintainers lack the bandwidth to do it right now since they’re focused on SnapChat infra integrations, so they are asking for contributions from the FOSS community to help with this. Getting v7 support in KeyDB could mean a potential seamless drop-in replacement upgrade path for current Fedora redis users and potentially less work for some Fedora package maintainers. So, if anyone reading this has the bandwidth to help out a potential upstream in rebasing to redis 7.2.4 (the last BSD licensed redis), it could benefit a lot of people inside and outside of Fedora/EL:

2

There is a live thread on the fedora devel list about this topic.

See Redis will no longer be OSS... now what? - devel - Fedora Mailing-Lists

3

Indeed. I had linked to it already in my OP, but no harm in making that thread more visible.

The TL;DR is that KeyDB getting v7 support would potentially solve the problem. KeyDB is open to outside help to make that happen, so if this impacts you and you know your way around redis, please consider helping upstream. Otherwise, we are going to have some difficult choices to make.