Copied my comment from dupe thread - but note that "Linux Foundation" is run by a bunch of Big Tech corporate interest[1] and not some sort of altruistic FOSS organization.
Hi, co-creator of Valkey here. I'm not that worried about it. There are a lot of people who have tried to maintain Redis folks, my employer AWS has one such fork I know very well, and they quickly become extremely hard to maintain with your own code. These aren't problems Redis wants to solve, they are off in their GenAI space building fancy extensions. For the next year or so it might be a real concern, but we are thinking long term, and I don't think it'll matter for long.
So, we thought the best approach was to stick with the license and get us into a vendor neutral foundation. We haven't ruled out LGPL, we just didn't make the change unilaterally and as a foundational part of the fork. We just want to keep building :)
You say that like it's a problem. Isn't the point of open source to be able to share so that others can take advantage of a solution to a given problem?
With the LLM craze there are some setups abusing redis as a (vector) DB. Please don't! Redis is a cache and wants to keep everything in RAM, eating GBs of RAM with relatively few entries. Keeping that manageable is also non-trivial so please just use a sane option like postgres for anything like that. https://redis.io/docs/management/optimization/memory-optimiz...
Readit News
[1]: https://www.linuxfoundation.org/about/leadership
redict is LGPL licensed, so that can't happen.
https://codeberg.org/redict/redict
So, we thought the best approach was to stick with the license and get us into a vendor neutral foundation. We haven't ruled out LGPL, we just didn't make the change unilaterally and as a foundational part of the fork. We just want to keep building :)
Deleted Comment