Do they expect people, but more importantly organizations and companies, trusting them again? Why would they use Redis over the independent fork Valkey?
this post was submitted on 03 May 2025
1 points (100.0% liked)
Linux
13563 readers
429 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
They'll stick to Valkey for the license alone. The AGPL is a good license, but the 3 clause BSD license is even more permissive which companies leeching off open-source like a lot more than the GPL licenses.
Support for one. Very often you need 24/7 support with an SLA for every part of the stack.
Maybe features? Not familiar with them, but often happens that enterprise features are behind an enterprise license. Stuff like LDAP integration, encryption with KMIP management, Kerberos, etc.
Third, management tooling. Monitoring, optimization, backups, debugging, what have you.
Most of the lemmy audience skews to Libre Software, but enterprise land doesn't care about all of the reasons listed in this thread, they were on the commercial license to begin with.
Nah, redis is dead to most devs, the forks are far more popular with indie devs now.
I'm working to move what I have to Valkey, no more rugpull games tyvm.
We did it Redis!!!
As someone that's a major fan of the AGPL-3.0 license, even I have a hard time believing that this would bring people back to Redis.
It's an upward battle from here on because they were the ones who chose to demolish their customer's trust.
Serious question- what do you use instead? Memcached is rock solid but has only like 5% of Redisβ feature set.
I think most people switched to Valkey which is a Redis fork:
Thanks for the info!!
The forks of proper redis.
I switched to keydb years ago, also a redis fork.
I don't use Redis or any alternative to be honest.
If I were pressed to choose; I'd honestly consider choosing Redis as the new AGPL-3.0 license is actually impossible to revert if development continues.
It's the usual combination of AGPL + CLA, they're allowed to relicense to any license of their choice at any moment. They've had the CLA in place since the previous SSPL license and the more-previous BSD license naturally allows that kind of stuff.
Valkey is already better
I worked on a project that was open source and then not and now is. The commhnity is gone. Maybe it's just because we're older.