【Hacker News搬运】取代Redis的竞赛
-
Title: The race to replace Redis
取代Redis的竞赛
Text:
Url: https://lwn.net/SubscriberLink/966631/6bf2063136effa1e/
文章讨论了Redis项目转向非自由、源代码可获得的许可证,特别是从Redis 7.4版本开始。这一变化引起了社区的广泛关注,因为现在有多个Redis的替代品可供选择,这些替代品都是自由软件,包括一个现有的分叉项目KeyDB和Linux基金会新宣布的Valkey项目。文章还回顾了Redis的历史,包括它的创始人Salvatore Sanfilippo(也被称为"antirez")的背景,以及Redis如何迅速成为流行的NoSQL数据库之一。文章还讨论了云服务提供商和开源社区之间的紧张关系,以及Redis Labs如何选择使用具有使用限制的许可证来保护其软件。最后,文章探讨了社区如何应对Redis的变化,包括对Linux发行版的影响,以及社区对替代品的看法。
Post by: chmaynard
Comments:
brody_hamer: 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!)<p>So we as developers don’t have to scramble to replace redis in our SAAS apps and web based software.<p>This is more about preventing AWS from eating their lunch by providing redis-as-a-service, without paying any sort of compensation to the redis developers.<p>Redis’ blog post: <a href="https://redis.com/blog/redis-adopts-dual-source-available-licensing/" rel="nofollow">https://redis.com/blog/redis-adopts-dual-source-available-li...</a>
brody_hamer: 直到我读了他们的博客,我才知道redis将在他们的“社区版”中免费使用,该版本将继续得到支持和维护(并得到改进!)<p>因此,作为开发人员,我们不必在SAAS应用程序和基于web的软件中争相替换redis<p> 这更多的是为了防止AWS通过提供redis即服务来吃午饭,而不向redis开发者支付任何补偿<p> Redis的博文:<a href=“https://;/;Redis.com/,blog/:Redis采用双源可用授权/”rel=“nofollow”>https:///;redis.com/;博客/;redis采用双源可用li</a>
klabb3: 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 <i>want</i> 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.<p>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.
klabb3: 为什么我们不尝试解决“不能用于bezos游艇”的许可证问题,而不是避开众多公司,尤其是那些<i>希望</i>以有意义的方式做好事的数据库公司?可用的源代码是好的,比我们通过aws获得的专有更好,但仍然不够。人们理所当然地害怕地毯拉,比如在付费产品中偷偷加入基本功能。我认为很多怀疑来自于这些未知<p> 但非歧视性的使用是意识形态上唯一的强硬路线。我想人们可以永远争论这个问题,就像GPL和copyleft之类的。但我的观点是,大多数人并不真正关心深层次的意识形态,而是想要一个健康的、对黑客和小企业友好的开源生态系统。理想情况下,一个简单、易懂的许可证,限制“转售你的产品”,而不是更多,你可以在没有法律团队的情况下对一个项目施加压力,就像麻省理工学院的许可证一样。
nerdponx: Isn't this the reason why AGPL has started to get more popular? Everyone has to play by the very strict rules <i>except</i> the copyright holder, who can do whatever they want, but the community still benefits from the core software being open source.<p>The BSD license in particular seems like a particularly bad way to run a business.
nerdponx: 是不是;这难道不是AGPL开始越来越受欢迎的原因吗?每个人都必须遵守非常严格的规则<i>,除了</i>版权持有者,他们可以做任何他们想做的事情,但社区仍然受益于核心软件的开源<p> 特别是BSD许可证似乎是一种特别糟糕的商业运营方式。
rokkitmensch: I so very much wish that Datomic had been licensed this way.
rokkitmensch: 我非常希望Datomic能以这种方式获得许可。
west0n: Neal Gompa opened a discussion on the Fedora development list, noting the license change and the need to remove Redis from Fedora.<p>Gompa also raised the issue on openSUSE's Factory discussion list.<p>After Docker was phased out, various distributions have adopted the compatible Podman as a replacement for Docker. It seems that a similar story is unfolding with Redis.
west0n: Neal Gompa就Fedora开发列表展开了讨论,指出了许可证的更改以及从Fedora中删除Redis的必要性<p> Gompa还提出了关于openSUSE;s工厂讨论列表<p> Docker被逐步淘汰后,各种发行版都采用了兼容的Podman作为Docker的替代品。Redis似乎也在上演类似的故事。