Live data from Hacker News

The race to replace Redis

lwn.net

331–340 of 520 posts

Re: The race to replace Redis

#331

Earlier quoted context omitted.

They dont't want AWS royalties. They wanna be able to command higher margins. Since AWS has lower costs and prices, Redis can't compete with good margins. The royalties are just a way to increase AWS costs, so that they raise their prices and give Redis the ability to keep high prices and margins, while still remaining attractive to customers (which don't have a cheaper choice anymore).

They want to make money with the software they built.

They want to make ludicrous profits on the software others have built for them.

There's nothing wrong with making money and being profitable. But they have to justify investments taken with greed. This license change is motivated by greed, not by "making money" fairly.

Re: The race to replace Redis

#332

It wasn’t clear to me until I read their blog, that redis will remain free to use in their “community edition”, which will continue to be supported and maintained (and improved!) So we as developers don’t have to scramble to replace redis in our SAAS apps and web based software. This is more about preventing AWS from eating their lunch by providing redis-as-a-service, without paying any sort of compensation to the re…

Yeah. As usual whenever something like this happens, there’s an endless supply of blatantly misleading FUD by open source license purists. Let’s not pretend that Redis has become unusable by….all but a few organisations selling hosted Redis solutions. The people who are “rushing” to replace Redis are probably doing so in a way that isn’t on their boss’s radar, and it’ll stay that way because their bosses would probably tell them to go do more important things.

Re: The race to replace Redis

#333

Earlier quoted context omitted.

The reality is that open search will be (if it is not already) more widely deployed and “battle tested” with bugs that production use raise resolved in it. The narrative that opensearch is some kind of unsafe abandonware is clearly nonsense when you read the commit log: https://github.com/opensearch-project/OpenSearch/commits/mai... All I can say is, sure, if you want elastic use elastic. …but opensearch is fine. I u…

How did you go from "It lacks so many improvements and advancements since the ancient version it was forked at" to "opensearch is some kind of unsafe abandonware"? Would love to learn the thought process here.

> Just use this pre-V1 public beta software I stumbled upon instead.

…but I mean, I’m not really up for playing the “pedantically correct about what he/she said” game with you.

Instead how about you comment on the point I’m actually making, which is:

opensearch is perfectly fine for most people.

For most people, there is no meaningful distinction between elastic and opensearch.

Opensearch is a healthy project which regularly receives updates and is widely used in production in large deployments.

If you have any meaningful or compelling argument why any of those three things is not true by all means, I’d love to hear about it.

Re: The race to replace Redis

#334
post #319

Earlier quoted context omitted.

*one of the creators. Being the first committer doesn’t mean he wrote all of the thing that is today called Redis. It’s a community effort and this is just as rude to the community that built it as they are claiming SaaS vendors are being to them by not “giving back”. This idea that you are owed reciprocity for publishing free software is about as logically sound as expecting compensation from someone when you give t…

> This idea that you are owed reciprocity for publishing free software is about as logically sound as expecting compensation from someone when you give them a gift. Ironically this happened because the community was using the BSD license instead of the GPL, when the former allows someone to fork the code under a different license . If the big cloud providers wanted to stick it to them, they would create their own for…

Yep. Precisely. Licenses are working as expected. People that spin this as “stealing” are simply showing their own lack of understanding.

Re: The race to replace Redis

#335

Microsoft's Garnet has the best chance of replacing Redis, the OSS project and the hosting company. Article doesn't mention it, but supposedly Microsoft uses novel algorithms and multi threading to achieve an order of magnitude improvement in throughput. Now if they can commercialize it with Azure, it should be a credible alternative to Redis Enterprise hosting.

To not support the FLUSHALL command suggests that Azure is the goal with the project.

Re: The race to replace Redis

#336
post #329

Earlier quoted context omitted.

You keep making comments about this, as if Redis was build from scratch by the company that is now making it closed source. They bought an open source project, and now that the original founder has stepped away they're trying to squeeze it for all they can. The "big corps" that you claim are using it to "pirate software in a legal way" (a) have been contributing to the formerly open source redis project, and (b) are…

Doesn't matter, they are the rigthfull owners of Redis and the author has freely given ownership to them, and has been paid for. Supermarket bills cannot be paid with pull requests.

Supermarket bills don't get paid by broken business models either. If Redis Inc never existed, Redis the software wouldn't be much worse for it. I'm starting to wonder who the entitled is in the first place.

Re: The race to replace Redis

#337

It wasn’t clear to me until I read their blog, that redis will remain free to use in their “community edition”, which will continue to be supported and maintained (and improved!) So we as developers don’t have to scramble to replace redis in our SAAS apps and web based software. This is more about preventing AWS from eating their lunch by providing redis-as-a-service, without paying any sort of compensation to the re…

> that redis will remain free to use in their “community edition”, I mean, they've already changed licensing for parts of the project twice in 6 years. I have zero faith that they won't pull a Vader and change the terms of the agreement again. > continue to be supported and maintained (and improved!) I'd guess that > 99% of any "improvements" Redis the company make, will affect As has been pointed out numerous times,…

KeyDB, the multithreaded fork of Redis, is already way faster as a KV store.

Re: The race to replace Redis

#338
post #323

Earlier quoted context omitted.

> the whole free software movement Eh no. What an overly broad generalization to read. Whether it is enough to make a living is another question, but that does not mean one must paint all of the communities the same color.

The fact that after 20 years this has become almost a daily discussion theme speaks for itself.

The problem is companies externalising development work on the boring parts of their software as "community edtions" and the like. That is a very distinct category of open source project and the only one that any of these discussions revolve around.

You seem to believe that all open source projects are in this category. That is not the case. You also seem to believe that there is always one company doing the most work and everyone else is just leeching off. That is also not the case.

Re: The race to replace Redis

#339

Earlier quoted context omitted.

I believe that Redis has an agreement of sorts with Salvatore Sanfilippo / Antirez, the creator of Redis.

Amazon / Google / Microsoft made a massive mistake by not hiring Antirez, it's chump change for them to throw him $1-2M a year at him so he can work on Redis for them full time.

They have engineering resources to maintain a fork, which they've made. https://github.com/valkey-io/valkey

Re: The race to replace Redis

#340

Microsoft's Garnet has the best chance of replacing Redis, the OSS project and the hosting company. Article doesn't mention it, but supposedly Microsoft uses novel algorithms and multi threading to achieve an order of magnitude improvement in throughput. Now if they can commercialize it with Azure, it should be a credible alternative to Redis Enterprise hosting.

No, it’s built using the .NET stack most Linux users won’t touch with a 20-ft pole.
Post reply on HN