Live data from Hacker News

The race to replace Redis

lwn.net

61–70 of 520 posts

Re: The race to replace Redis

#61

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…

I continue to have mixed feelings about this kind of thing.

A (very) long time ago the Apache developers could have gone down this route.

> You can only run Apache under very specific circumstances!

Or memcached:

> You are only allowed to run a memcached server if you're only caching your own website!

We see how nonsensical this is

Re: The race to replace Redis

#62
post #56

I’m usually pretty ambivalent when a company decides to move to a license like BUSL. Sure it’s not “free” - but practically it only affects the likes of AWS from freeloading while making extraordinary profits. Especially true when a given company started the project. I understand why some hold strong feelings on the principles of OSS. My perspective is we’ll have fewer nice things if we allow the likes of AWS to cann…

Seems similar to what Elastic did few years ago [1]. I kinda understand their motivation. It's not theirs originally, but they had antirez working on it for 5 years as their employee. They are making some contributions [2], I wish GH had a way to see such an insight by company affiliation. On the other hand, AWS and likes can easily fork pre-license-change version and spin it into its own product. However, I am fairl…

AWS did not launch their own spinoff alone, but instead joined the Valkey project by the Linux Foundation[0], alongside many other major contributors:

> Industry participants, including Amazon Web Services (AWS), Google Cloud, Oracle, Ericsson, and Snap Inc. are supporting Valkey. They are focused on making contributions that support the long-term health and viability of the project so that everyone can benefit from it.

Seems like a good alternative to a single company's spinoff: Many major providers working on this same project should result in everyone benefiting from it.

https://www.linuxfoundation.org/press/linux-foundation-launc...

Re: The race to replace Redis

#63
post #56

Earlier quoted context omitted.

Seems similar to what Elastic did few years ago [1]. I kinda understand their motivation. It's not theirs originally, but they had antirez working on it for 5 years as their employee. They are making some contributions [2], I wish GH had a way to see such an insight by company affiliation. On the other hand, AWS and likes can easily fork pre-license-change version and spin it into its own product. However, I am fairl…

AWS did not launch their own spinoff alone, but instead joined the Valkey project by the Linux Foundation[0], alongside many other major contributors: > Industry participants, including Amazon Web Services (AWS), Google Cloud, Oracle, Ericsson, and Snap Inc. are supporting Valkey. They are focused on making contributions that support the long-term health and viability of the project so that everyone can benefit from…

I don't have any inside knowledge, but I can't believe that they don't have an internal fork of Redis for Elasticache.

Re: The race to replace Redis

#64
post #2

I'd be more interested in the race to build a business model that works with open source and venture funding, myself. A grand unified theory of software goods funding, if you will.

I wonder if software really deserves its own economics. If you haven't read Hal Varian's Information Rules , I highly recommend it. Check the publication date, then read it anyway, then reflect on the publication date when you're done. I found it very worthwhile.

Thanks for the recommendation, I downloaded it & started reading and yes it's a treasure trove.

Re: The race to replace Redis

#65

I’m usually pretty ambivalent when a company decides to move to a license like BUSL. Sure it’s not “free” - but practically it only affects the likes of AWS from freeloading while making extraordinary profits. Especially true when a given company started the project. I understand why some hold strong feelings on the principles of OSS. My perspective is we’ll have fewer nice things if we allow the likes of AWS to cann…

[deleted]

Re: The race to replace Redis

#66
post #3
post #2

I'd be more interested in the race to build a business model that works with open source and venture funding, myself. A grand unified theory of software goods funding, if you will.

Yep. Been wondering where this is headed with the recent YC batch posts claiming they are gonna be all opensource and make money on cloud offering

[deleted]

Re: The race to replace Redis

#67
AWS also forked ElasticSearch into their “OpenSearch” DBaaS. It caused some issues at my last job because OpenSearch limited us to a particular version of the NEST .NET library that was missing some newer functionality. Real bummer and feels like a step in the wrong direction given all we’ve accomplished in tech over the last 20 years.

Re: The race to replace Redis

#68

Isn't this the reason why AGPL has started to get more popular? Everyone has to play by the very strict rules except the copyright holder, who can do whatever they want, but the community still benefits from the core software being open source. The BSD license in particular seems like a particularly bad way to run a business.

I see more of a shift to open core.

Many large orgs just say no to viral licenses, and in choosing AGPL, you put blockers to adoption.

Open core releases some of the project under permissive license, and keeps some private or under a permissions license.

We are all still trying to figure out how we can have sustainable open source where people can be paid to work on it full time

Re: The race to replace Redis

#69
post #54

Earlier quoted context omitted.

Well, except for the fact that "redis" the organization didn't create redis and isn't even the main developer of redis. The origin of Redis the company is literally as a hosting provider for the open source redis that they didn't create.

This is what I am confused about so what right do they have to enforce AWS from selling Redis when they do not own it?

The licensing change only applies to their future versions which they own all contributions of which AWS won't be allowed to leech off anymore.

Re: The race to replace Redis

#70
Why don’t we try to fix the “cannot be used for bezos yacht”-licenses instead of shunning the numerous companies of especially databases who want to do good in a meaningful way? Source available is good, better than proprietary which is what we get with aws, but still not enough. People are legitimately afraid of rug pulls, like sneaking in essential features into paid offerings. I think a lot of the skepticism comes from those unknowns.

Afaik the non-discriminatory use is the only ideological hard line. I guess people can debate that forever, like with GPL and copyleft and such. But my edgy take is that most people don’t really care about deep ideology yet want something that promotes a healthy hacker- and small-business friendly open source ecosystem. Ideally, a simple, well-understood license that restricts “re-selling your product” and not much more, that you can slap on a project without a legal team, just like with the MIT license.

Post reply on HN