Hopefully this will help resume work on a better High Availability code. Where one could have a cluster of 3 ValLey servers, with a superior HA protocol.
Valkey Is Rapidly Overtaking Redis
21–30 of 90 posts
Re: Valkey Is Rapidly Overtaking Redis
#22Redis holds such a special place in my heart. It was the definition of awesome, open-source software. It always felt like Redis was THE definition of open source. The fact that the license has changed is heart-breaking.
Re: Valkey Is Rapidly Overtaking Redis
#23Saw a presentation by them at this week's Open Source Summit. Seems like a lot of the major contributors to Redis have moved over to this project. And it seems like AWS is a major supporter of it. I suspect their Elasticache Redis will soon be Elasticache Valkey.
Re: Valkey Is Rapidly Overtaking Redis
#24Re: Valkey Is Rapidly Overtaking Redis
#25"Rapidly", so most people don't even know the story about Redis changes and I would say 99.99 never heard about Valkey.
At the company, I mentioned Valkey, and no one had any clue what I was taking about (we use Redis).
Re: Valkey Is Rapidly Overtaking Redis
#26"Rapidly", so most people don't even know the story about Redis changes and I would say 99.99 never heard about Valkey.
We are experiencing exponential growth in the last week, going from 1 user to 2.
Relevant xkcd https://xkcd.com/605/
Re: Valkey Is Rapidly Overtaking Redis
#27"Rapidly", so most people don't even know the story about Redis changes and I would say 99.99 never heard about Valkey.
Redis (64.7k stars): Excluding merges, 8 authors have pushed 8 commits to unstable and 10 commits to all branches. On unstable, 173 files have changed and there have been 2,002 additions and 3,194 deletions.
Valkey (12k stars): Excluding merges, 41 authors have pushed 147 commits to unstable and 181 commits to all branches. On unstable, 473 files have changed and there have been 10,635 additions and 9,663 deletions.
You may as well just start mentally teaching yourself to alias redis to valkey.
Re: Valkey Is Rapidly Overtaking Redis
#28Re: Valkey Is Rapidly Overtaking Redis
#29Earlier quoted context omitted.
There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis. 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
I was honestly shocked by this too, I never intended Sidekiq users to left in a lurch like this. It took them over three years from the RESP3 release before their service supported it. I figured any good SaaS should be dogfooding their own releases, but I guess not!
Having not heard of any of this before now, I'm struggling to wrap my head around why this would be evidence that they're not good stewards of Redis-the-project (as opposed to their Redis service). If they had delayed the general release until their cloud could support it or tried to expedite their cloud release by moving resources over to the cloud services, I feel like that would be much more worrisome in terms of their stewardship of the project as a whole. If anything, it sounds like they basically chose to prioritize Redis in general over their own offering, which is exactly what I'd expect people in the community to want.