Redis has decided to move away from BSD license to dual-license Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1), ignoring many historical failures where other companies tried to move away from open source licenses (ElasticSearch vs OpenSearch, MySQL vs MariaDB, Oracle JDK vs OpenJDK, OpenOffice vs LibreOffice, Terraform vs OpenTofu etc.).
The decision has not gone down well within the redis community.
Any Redis users in our community? What are your thoughts on this issue?
This discussion was created by janrinok (52) for logged-in users only, but now has been archived.
No new comments can be posted.
Redis Changes License From BSD-3 to Dual RSALv2+SSPLv1
|
Log In/Create an Account
| Top
| 6 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
(1)
(Score: -1, Troll) by Anonymous Coward on Sunday March 24 2024, @09:19PM
I nearly fell asleep reading the summary. "in-memory data structure store"
(Score: 4, Interesting) by requerdanos on Monday March 25 2024, @01:25AM (1 child)
Redis USED TO BE an open source, etc., etc., but is no longer such a thing. Older versions released under free licenses will still be free, but any newer versions are proprietary.
(Score: 4, Interesting) by canopic jug on Monday March 25 2024, @09:34AM
Another way to look at it is that Redis has been renamed to Redict [andrewkelley.me], at least in practice. Redis has been taken out of circulation and made proprietary. Drew's now maintains a fork of the original code base, along with a new license, reflects the original goals of the project's founder. Furthermore, the Redict fork continues the original FOSS lineage [redict.io] unlike this proprietary move.
All that said, there are other key-value databases out there. One of the more tried and true, but low profile, key-value databases out there would be YottaDB [gitlab.com]. I hope that most who formerly used Redis make the move to Redict and contribute to it with code or funding. However, this is also an opportunity to look around at what else is out there.
Money is not free speech. Elections should not be auctions.
(Score: 4, Informative) by boltronics on Monday March 25 2024, @03:06AM
For applications that just need something purely for caching, I'm looking at switching those over to memcached. I was already looking at this before the news broke, since I already have a memcached server for other projects and it doesn't make sense to have both — provided the additional features that Redis includes are not being used.
I also prefer to just use software that's included in Debian, without having to manage 3rd party repositories.
However, I have no doubt that Amazon will fork it as they did ElasticSearch -> OpenSearch for AWS. Ut looks like this is already in progress here [github.com].
"Started by former Redis contributor(s) and AWS employees. BSD 3 Clause license" according to this [me.dm] Mastodon post.
It's GNU/Linux dammit!
(Score: 2) by Rich on Monday March 25 2024, @01:02PM
Question to the licence experts: Where is this SSPL different from the AGPL?
I read over the "ssplisbad" site and despite the writer whining that the wording is unclear, the licence pretty much clarifies that with "all such that a user could run an instance of the service using the Service Source Code you make available". So you have to open the service source and anything that's needed to run it. Sounds like AGPL to me. Or is the AGPL more lenient with having to open the dependencies?
(Score: 2) by VLM on Monday March 25 2024, @04:31PM
It was inevitable, growth stopped a decade ago
https://db-engines.com/en/ranking_trend/system/Redis [db-engines.com]
This is not precise, but the days of redis doubling in use every 18 months ended around the end of Obama's presidency. Stick a fork in it, it's done, its growth-era is not coming back. Everything that's going to use redis was written before 2015, more or less, or at least new stuff is barely keeping up with stuff ending or changing to newer technologies.
If you can't make money off growth or realistically anticipated growth, you gotta make money by squeezing the remaining users for what they got while you can squeeze them before they leave. See recent years of VMware, for an example, or for a much older example, SCO Unix.
They "have" to do something to keep the lights on as long as possible. If you are still stuck using redis for various legacy or business requirements, it was already time to start looking for the fresh new replacement and this just makes it more urgent.