Live data from Hacker News

Redis is open source again

antirez.com

101–110 of 815 posts

Re: Redis is open source again

#101
post #68

I'm curious whether the community will trust Redis-the-company again after this, or if they'll choose to stick with Valkey. The other concern is at least some big company legal departments are wary of AGPL software, which makes Valkey, still BSD, more attractive to them. Edit: Regardless, thank you and the rest of the folks inside Redis for pushing to bring this back to OSS!

Statistically nobody is using valkey.

Yeah, all the open source distributions and most open source projects switching to valkey must be "nobody".

Re: Redis is open source again

#102
post #68

Earlier quoted context omitted.

Statistically nobody is using valkey.

Are there usage stats available? How do you know this?

My guess is they are making it up. AWS has no public information, but there are some high profile customers that have migrated https://aws.amazon.com/elasticache/customers/.

Re: Redis is open source again

#103
post #82

Earlier quoted context omitted.

Are there usage stats available? How do you know this?

My guess is most people are using Redis via cloud providers. Did any cloud providers switch away from Redis?

Wasn’t the whole point (or one of the major ones) of Valkey so that AWS could use it?

Re: Redis is open source again

#104
post #64

Earlier quoted context omitted.

fool me can't get fooled again But in seriousness, the chances of valkey going closed source are low. It's run by Linux Foundation. It would be like suggesting that Node.js might go closed source...

They were obviously making a tongue in cheek comment instead of seriously suggesting Valkey may go proprietary.

And it was so absurd that it didn't land with me, even though most of the time I notice these sorts of things. Ah well.

Re: Redis is open source again

#105
post #68

I'm curious whether the community will trust Redis-the-company again after this, or if they'll choose to stick with Valkey. The other concern is at least some big company legal departments are wary of AGPL software, which makes Valkey, still BSD, more attractive to them. Edit: Regardless, thank you and the rest of the folks inside Redis for pushing to bring this back to OSS!

Statistically nobody is using valkey.

If you use the latest versions of Redis, you are benefiting from the continued efforts of the Valkey development community. [1]

This is Open Source working well.

Unfortunately, the reverse flow does not work.

[1] https://github.com/redis/redis/pull/13638

Re: Redis is open source again

#107
post #33

I contributed a minor (but imho still neat :p) improvement to Redis under its original license, and personally moved to using redict when the unexpected license change to SSPL was announced - and I was feeling betrayed as a contributor to a properly-FOSS-codebase. (Had they switched to AGPL right away, I'd have been perfectly fine with that change from a moral perspective, ftr.) I have a great deal of respect for ant…

Microsoft made one called Garnet, I wouldn't say its a fork though, its basically compatible with Redis and implemented mostly in C#. It supports the RESP wire protocol from Redis for ease of compatibility. https://github.com/microsoft/garnet

You do see how that's even worse, right?

Re: Redis is open source again

#108
post #107

Earlier quoted context omitted.

Microsoft made one called Garnet, I wouldn't say its a fork though, its basically compatible with Redis and implemented mostly in C#. It supports the RESP wire protocol from Redis for ease of compatibility. https://github.com/microsoft/garnet

You do see how that's even worse, right?

I don't see how it's worse?

https://github.com/microsoft/garnet/blob/main/LICENSE

It's MIT licensed?

Re: Redis is open source again

#109
Mesmerizing number of views. I must admin I refreshed the page multiple times to see the count increase. If I increased the view count several times, I must admin I did not read the article multiple times.

Re: Redis is open source again

#110
post #51

Earlier quoted context omitted.

Your company invested hundreds of engineering hours switching from Redis to a clean fork of Redis?

At the very least you have to validate everything that touches redis, which means finding everything that touches redis. Internal tools and docs need to be updated. And who knows if someone adopted post-fork features? If this is a production system that supports the core business, hundreds of hours seems pretty reasonable. For a small operation that can afford to YOLO it, sure, it should be pretty easy.

But why are they spending any time switching away from Redis at all unless they are a hosting provider offering Redis-as-a-service?

I wasn't aware the license had any negative affect on private internal use.

Post reply on HN