Live data from Hacker News

Valkey Is Rapidly Overtaking Redis

devops.com

11–20 of 90 posts

Re: Valkey Is Rapidly Overtaking Redis

#11
post #8
post #3

The 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.

I’m amazed that they thought that they could do this and get away with it. Redis is almost a foundational tool for modern caching architectures. Every company I’ve ever worked at used redis like candy to cache stuff that wasn’t important enough for the reliable but expensive and slow data stores. Additionally, the main features 99% of people want and need have been in redis for a decade. Even a fork that only fixed s…

> Even a fork that only fixed security bugs will have done better than Redis Labs after this debacle

This describes Redict, not Valkey. I think it's actually great we have two forks, so they can focus on different things.

Re: Valkey Is Rapidly Overtaking Redis

#13
post #9

Is 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.

One is maintained and the other isn't. If you don't care about that you could definitely stick with the old version.

Redis hasn’t materially changed since about 2.8 so tbh unmaintained is more than fine.

Re: Valkey Is Rapidly Overtaking Redis

#14
post #6
post #2

Good. I hope Redis Labs dies a slow death for stealing the project from the community.

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!

Re: Valkey Is Rapidly Overtaking Redis

#15
post #14
post #6

Earlier 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!

This is a very common but wrong assumption.

The OSS and Cloud divisions of most companies are very different beasts. The engineers that staff them are different, and their focus is different. This has often lead to issues where the company that creates the project doesn’t always have the capability to support it at scale.

TBH, while I don’t support that kind of behavior, the cloud providers probably provide the best SaaS support for most OSS projects, just because of the operational capabilities they have created.

Re: Valkey Is Rapidly Overtaking Redis

#16
LOL, Redis CEO Rowan Trollope. Man I despise that guy. After successfully navigating the Cisco Contact Center, UC and WebEx business into oblivion, he ends up at Five9 architecting the crash and burn Zoom acquisition that failed 'successfully', and now he pops up at Redis.

Run away screaming as fast as you can.

Re: Valkey Is Rapidly Overtaking Redis

#19

Is 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.

Maybe take a look at the other fork, Redict?

https://redict.io

Re: Valkey Is Rapidly Overtaking Redis

#20
post #16

LOL, Redis CEO Rowan Trollope. Man I despise that guy. After successfully navigating the Cisco Contact Center, UC and WebEx business into oblivion, he ends up at Five9 architecting the crash and burn Zoom acquisition that failed 'successfully', and now he pops up at Redis. Run away screaming as fast as you can.

I'm curious. Do you have a summary which goes over that without having to read a dozen articles?
Post reply on HN