Live data from Hacker News

The race to replace Redis

lwn.net

161–170 of 520 posts

Re: The race to replace Redis

#163
post #128

Earlier quoted context omitted.

AWS leeches as much as Garantia Data no?

If you own copyrights you’re not the leech.

If you own the copyrights you had money to spend at some point. Other than that unless you are one of the contributors you are leeching, just different flavors of leeching.

Re: The race to replace Redis

#164

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.

The whole move to new "open-core" licenses started with the most famous (infamous?) AGPL project - MongoDB. The AGPL is not what companies like this want (Mongo, Elastic, Redis etc). They don't want AWS's code: AWS is already providing that. They want AWS to pay them royalties or stop competing.

> They want AWS to pay them royalties or stop competing.

But the switch from AGPL to SSPL didn't do either of those things.

AWS still built DocumentDB to compete with Mongodb, and didn't use any SSPL OR AGPL code in the implementation (at least according to their FAQ[1]). And AFAIK AWS isn't paying mongo any royalties.

[1]: https://aws.amazon.com/documentdb/faqs/

Re: The race to replace Redis

#165

Earlier quoted context omitted.

> re-selling your product” and not much more That's not what AWS is doing. AWS is selling management services. The fact that managed DBs are as popular as they are says this is a significant value add.

And that's also how DB companies try to monetize. So a hyperscaler offering this directly really undermines your entire business. In the past you could offer a Enterprise version with support, but with the move to the cloud that market is shrinking and Amazon is eating the new market themselves

> And that’s also how DB companies try to monetize

Open source DBs have been around a while, though. A minority of them trying to pay the bills with monopoly rents on hosted services is… much newer. Its how VC-backed DB-as-central-tech startups try to monetize, and, yeah, if you are going to do that, you need a proprietary license.

But don’t expect people to treat your DB like an open source DB, then, either. You can be Oracle instead of Postgres, but you can’t also expect to get treated like Postgres, instead of Oracle.

Re: The race to replace Redis

#167

Earlier quoted context omitted.

Certainly not a new idea. As recently as early 1990s I licensed shareware that had terms requiring corporations to pay for a license with different fees and/or restrictions as those for individual, non-commercial users. Somehow this ideal was lost. Today, software authors seems allegiant to so-called "tech" companies, not to individual, non-commercial end users. As a non-commercial end user, I would prefer to use ver…

No, a non-commercial license is not a natural born person only license. If you're a human you get to use the GPL to your hearts content. If you're a corporation you do not. It's not a hard concept to understand, but it does mean people can't steal from the commons so they spend a lot of time trying to not understand it.

I would have to look at the terms to understand. Your comment just reminded me of those sharware-era non-commercial licenses. That's all. Did not intend to suggest the license you mentioned is similar or the same in any other respect than having different license terms for commercial entities versus other users.

Re: The race to replace Redis

#168
post #161

Why don't the distros just take the last free version and fork from there.

Isn't that what redict is?

I see that it is. So then I don't see what the hoopla is about at all.

The software is all there. Some dickheads forked a proprietary version. They got the name, which will be their consolation prize in their voyage to irrelevance; nice knowing you.

Meanwhile, what everyone uses marches on.

Re: The race to replace Redis

#169

I feel copyleft licenses look more favourable at this point of time. What’s the value of more free/business friendly licenses if you can’t guarantee that the same license will apply for all the future releases? Looks more like a bait and switch policy.

Am I right in understanding that the relicensing was possible because of the CLA, not just because of the BSD license? Would a permissively licensed project that didn't use a CLA be vulnerable in the same way?

A key concern is that BSD isn't viral, so anyone can take BSD Redis and fork it into a commercial offering. If you want to, you can. The Redis trademark prevents anyone but Redis the company from calling their fork "Redis".

A CLA may impact relicencing, it depends on the terms. A simple CLA may only say "I am the owner of the code and I release it under $LICENSE". The current Redis CLA also has a copyright grant, which gives Redis the company greater rights.

Re: The race to replace Redis

#170
post #54

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…

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.

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