-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider a Redis alternative due to the use of the SSPL #5827
Comments
Side note: Because the redis definition in the docker-compose just specifies That version introduced a new save file format that is incompatible with valkey, so any migration would likely involve rebuilding the redis data now. |
Another reason to move to a free open source alternative! |
I've raised this in our internal mailcow channel to discuss. If anyone happen to know a (easy) migration path, please let us know. |
With commit 35a6f81 we have now pinned reddit 7.4.2 (what is what There are a few possible migrations from redis 7.4 to valkey outlined here: valkey-io/valkey#845 (comment). While not supported by Valkey natively, this could be a way getting to a different redis-alternative... |
KeyDB is has been an awesome Redis alternative for us. https://docs.keydb.dev/ |
Summary
A some point in the future it would no doubt make sense to move from the now non-free Redis to an alternative.
The LGPL Redict looks promising, containers are available already.
The BSD Valkey has the support of the Linux Foundation and big cloud capital.
Motivation
At some point Linux distros will stop shipping Redis due to the license change to the SSPL.
Additional context
No response
The text was updated successfully, but these errors were encountered: