Live data from Hacker News

Valkey Is Rapidly Overtaking Redis

devops.com

31–40 of 90 posts

Re: Valkey Is Rapidly Overtaking Redis

#32
post #4

"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.…

How are we supposed to interpret these numbers? In its whole history, Redis has had 8 contributors? And in less than a month Valkey has added 33 contributors?

Re: Valkey Is Rapidly Overtaking Redis

#33

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

I would personally never contribute to a project with non-free license without getting paid. It's basically working for a company without pay.

Re: Valkey Is Rapidly Overtaking Redis

#34
post #7

One of the challenges Redis labs here have is that there's very little reason for their userbase to stay loyal to them. antirez 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…

Here's some additional insights regarding Redis and Valkey

https://devboard.gitsense.com/redis?id=f66d8a46ef

If you ignore comments and just look at people raising issues and pull requests, Valkey has more contributors

https://devboard.gitsense.com/redis?id=f66d8a46ef&comments=i...

Full disclosure: This is my tool

Re: Valkey Is Rapidly Overtaking Redis

#35
post #4

"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.…

But what value have those 8 vs 41 authors added to the project with those changes? I think that's the primary concern here.

Re: Valkey Is Rapidly Overtaking Redis

#36
post #33

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

I would personally never contribute to a project with non-free license without getting paid. It's basically working for a company without pay.

The problem is that an open source project you contribute to can become non-free from under you at any point. This pattern is becoming more and more common now.

Re: Valkey Is Rapidly Overtaking Redis

#37
post #36
post #33

Earlier quoted context omitted.

I would personally never contribute to a project with non-free license without getting paid. It's basically working for a company without pay.

The problem is that an open source project you contribute to can become non-free from under you at any point. This pattern is becoming more and more common now.

There are ways to prevent that which in retrospect we should have paid more attention to. For example, (L)GPL with no CLA cannot be changed later.

Re: Valkey Is Rapidly Overtaking Redis

#39
It's too dangerous to build a company around open source. You're trapped between AWS eating you or having to relicense and AWS eating you. Source-available from the beginning protects you from this. The problem with OSS stuff is that people are generally price-sensitive and you can't beat the platforms for this since they get the R&D for free.

It's sort of how I don't hire junior people. When others have trained them up, I can just hire them for more. The other guys have to pay to train them so they hope to get some reward for that, but switching costs are low. I can just take pre-trained guys.

And just like the pre-trained guys in this scenario, AWS can always offer a better deal. You need to moat your stuff in some way. Elastic License is ideal if you want to build a company around this. If you just want to make things for the good of mankind or whatever, you can use BSD/GPL/MIT/whatever, but you're doomed if you want to build a company around those licenses.

Elastic made it by being quick to the jump. Others have followed. The only really successful model that's different has got to be Kong and RHEL and they've both been around a while. Kong's adoption is troubled because once you get successful, using their OSS thing is better than the enterprise because their pricing tiers go up. But they seem to have good enterprise sales team. Don't know about RHEL.

But if I were starting a company around this stuff, I'd be very careful about having core tech be true OSS. Source-available yeah, but true OSS is too risky.

Re: Valkey Is Rapidly Overtaking Redis

#40
post #36
post #33

Earlier quoted context omitted.

I would personally never contribute to a project with non-free license without getting paid. It's basically working for a company without pay.

The problem is that an open source project you contribute to can become non-free from under you at any point. This pattern is becoming more and more common now.

This is only half true in my opinion. Only future versions will be non-free, all the contributions before the license change stay free and can be forked.

Any project with a permissive license (BSD/MIT) can always be made into a commercial product. I could fork Valkey any minute, change the name and start selling it.

Post reply on HN