Valkey Is Rapidly Overtaking Redis
devops.com
Valkey Is Rapidly Overtaking Redis
1–10 of 90 posts
Re: Valkey Is Rapidly Overtaking Redis
#2Re: Valkey Is Rapidly Overtaking Redis
#3Re: Valkey Is Rapidly Overtaking Redis
#4Re: Valkey Is Rapidly Overtaking Redis
#5Re: Valkey Is Rapidly Overtaking Redis
#6Good. I hope Redis Labs dies a slow death for stealing the project from the community.
It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594
Re: Valkey Is Rapidly Overtaking Redis
#7antirez retired from Redis development a few years ago.
From https://github.com/redis/redis/graphs/contributors it looks like activity since he left has been mostly from people who didn't overlap with him much.
Redis Labs have not shown themselves to be outstanding stewards of the project as far as I can tell. Why shouldn't people support the fork?
Re: Valkey Is Rapidly Overtaking Redis
#8The biggest mistake Redis Labs made was doing a rebrand at the exact same time as a license change. Usually you want rebrands to be loud and well known and license changes to be silent and ignored until it's too late and people have adopted the new license. In this case, they loudly announced that they're making an unpopular change and it gave everyone the will to switch.
Re: Valkey Is Rapidly Overtaking Redis
#9Is there any reason I don’t just stick with redis 7.2.4 instead of trusting redict/valkey to not inject some backdoor trash? I can avoid the corporate pivot and the random fork at the same time.
Re: Valkey Is Rapidly Overtaking Redis
#10Is there any reason I don’t just stick with redis 7.2.4 instead of trusting redict/valkey to not inject some backdoor trash? I can avoid the corporate pivot and the random fork at the same time.