Valkey Support

As long as Valkey remains API compatible with original Redis, there's no reason why you shouldn't be able to use it.

Automatically closed - issue fixed for 2 weeks with no activity.

Thank you @Berdir :)

The Ubertus team, including myself, are also interested in support for Valkey.

For those not familiar with https://valkey.io it is a successor to Redis. Details at https://en.wikipedia.org/wiki/Valkey

The challenge with the latest Redis is that they modified its license from BSD-3-Clause to RSALv2 and SSPLv1 on March 20th, 2024. "This prompted a large portion of the user and developer community, including contributors from Alibaba Group, Amazon, Ericsson, Google, Huawei and Tencent, to fork the code of Redis 7.2.4 as a project of the Linux Foundation under the new name Valkey, retaining the BSD license.[3] Valkey 8.0, released six months after the fork, featured improved threading and significantly improved performance."

A couple of comments, though:

• Redis ⪚ 8.0 is available under the open source AGPLv3 license too, not just the non-open ones
• The toxigon.com link attempts to install suspicious extensions to the browser: either they are compromized, or doing it willingly. So beware that link. Disabling JS allows one to see the page.

> Redis ≥ 8.0 is available under the open source AGPLv3 license too, not just the non-open ones

The problem is that hosting platforms such as platform.sh and also general cloud platforms like AWS and so on can no longer provide redis as a service.

That said, I don't really get what #5 is trying to say. valkey is compatible with phpredis and so on, there is no indication that this module wouldn't be compatible with valkey out of the box. If you see any indication that this isn't the case, then open a bug report with specifics and extend our gitlab CI test coverage to test against valkey. Otherwise, just test it and switch.

https://github.com/ddev/ddev-redis/issues/28

Hello @berdir :) My first reply is below

I don't really get what #5 is trying to say.

Thanks for both your reply and all your contributions as maintainer of the fabulous Drupal module Redis. In my comment #5 I was trying to say that both me and the Ubertus team are also interested in a new feature for the Drupal Redis module to support Valkey. After your comment #7, I now understand that the Redis Drupal module presently support Valkey. This is great news :) Assuming Valkey remains API compatible with original Redis.

BTW, in the future, if the Redis Drupal module needs to be adapted to support both Redis and Valkey, if needed, as volunteers, the Ubertus team, including myself, would be happy to contribute beta testing and documentation.

@berdir :) My second reply is below

Redis ≥ 8.0 is available under the open source AGPLv3 license too, not just the non-open ones

This is also my understanding. Maybe my comment #5 was not clear. I will try to clarify below.

In my comment #5, I meant that one big strength of Valkey is that it is legally controlled by a friendly NOT-for-profit organization. Which, as you know, is called "Linux Foundation" :) Usually, NOT-FOR-profit organizations value you the people above money. For both you and all user of Valkey, this means LOWER risk of future Lock-In.

In comparison, the Redis engine is legally controlled by the FOR-profit organization called "Redis Ltd". Usually, a FOR-profit organization is at higher risk to value money above people :( In turn, this means HIGHER risk of future Lock-In. This is what I meant by "challenge".

As for the Drupal module Redis, as you know, it presently supports both the Redis engine and the Valkey engine. So end-users are able to choose one engine to their liking. Which is great :)

Below is the same as above. But with details and sources for those interested or those not familiar with Redis and Valkey engines.

What do I mean by "risk" above? The company "Redis Ltd." has a long history of behaviors that risked to value money above you the people. In other words, the Redis Engine has a history of repeating risk of Lock-In.

What do I mean by "long history"? It is not the first time that "Redis Ltd." tried to change the license of Redis engine. This summarized chronological timeline clarify this recurring risk of Lock-In with Redis engine:

1. In 2018 was one of the first time that "Redis Ltd" tried to change the license on some of its Redis engine modules. In other words, "Redis Ltd" started trying to add a Lock-In. Source:
• https://www.cyberkendra.com/2024/03/redis-shifts-to-dual-licensing.html
___• https://archive.ph/VTs8G
• https://redis.io/blog/redis-license-bsd-will-remain-bsd/
___• https://archive.ph/rVb3O

2. March 2024, again, "Redis Ltd" tried to change the license of the Redis engine. Again, tried to add a Lock-In.

3. Most users of libre source software don't like any types of Lock-In. As a result, after the 2024 event above, the Redis community forked Redis engine into Valkey engine with a fully libre source license with LOWER risk of Lock-In. Valkey, as you know, is a drop-in replacement for Redis engine.

4. After the fork above, a very large part of the community moved from the increasingly risky Redis to the safer Valkey.

5. On March 20, 2024, both after the community forked Redis into Valkey, and after a large amount of the community moved from the risky Redis to the safer Valkey,"Redis Ltd." announced that it reverted Redis engine license from not fully libre source to fully libre.

6. In the future, will "Redis Ltd" try again to somehow add Lock-In to Redis engine or any of its dependencies? To resolve this challenge, my suggestion, for the users' consideration and for their decision, is to shift from Redis engine to Valkey engine. Because, Valkey is safer and at LOWER risk of Lock-In.

Source about "Linux Foundation" is a NOT-for-profit organization. A LOWER risk to value money above people. In turn, at LOWER risk of Lock-Ins:

• https://en.wikipedia.org/wiki/Linux_Foundation

___• https://archive.ph/MCBEE

Source about "Redis Ltd" is a FOR-profit organization. A HIGHER risk to value money above people. In turn, at HIGHER risk of Lock-Ins:

• https://en.wikipedia.org/wiki/Redis_(company)

___• https://archive.ph/MVkI0

This is a note to myself: ID_S2H3N3V9

Hello @fgm :) My replies are below

The toxigon.com link attempts to install suspicious extensions to the browser: either they are compromized, or doing it willingly. So beware that link. Disabling JS allows one to see the page. 

Thanks for your reply. Feel really free, in any ways to your liking, to view or not view this page. From my end, I always use both the uBlock Origin and NoScript modules. Which deactivate JavaScript (JS) on all pages by default. In the case of this page, I'm able to view it with both module activated. In other words, JS deactivated. It is maybe a browser thing. I'm using LibreWolf. Which is powered by Firefox.

Redis ≥ 8.0 is available under the open source AGPLv3 license too, not just the non-open ones

This is also my understanding. My central point is that the Valkey engine is a lower risk of Lock-In. Maybe my comment was not clear about this.

My same answer but with details and sources are in my #10 if you're interested in those

It's not directly related to this issue, but this blog post has given some ideas to me:

https://www.gomomento.com/blog/valkey-turns-one-how-the-community-fork-l...

Thanks #@orkut murat yılmaz for sharing the information in your comment #12 ✨ Valkey Support Active . Interesting read.

Those test results published by Khawaja Shams, show, once more, that people contributing to a libre source software are more valuable than Lock-In. In other words, you and all contributors are the most valuable asset to a libre source software. Putting people above money is a winning strategy.

I agree with Khawaja Shams on this:

Valkey is not only thriving, but now outperforming Redis 8.0 in real world benchmarks.

The Ubertus team confirmed this outperforming on multiple products migrated to Valkey. Either outperforming or equal.

Those test results above also add a benefit for users of the Drupal Redis → module about adapting it to support both Redis and Valkey. I mean, in the future, if somehow the Drupal Redis module needs to be adapted to support either the present (#8) ✨ Valkey Support Active or a future version of Valkey, those interested could benefit from potential faster performance with Valkey. Per my previous comment, in the future, if needed, as volunteers, the Ubertus team, including myself, would be happy to contribute beta testing and documentation about adapting this Drupal Redis module.