Redis Returns To Open Source After Year-Long Proprietary Detour (thenewstack.io)
- Reference: 0177256189
- News link: https://news.slashdot.org/story/25/05/02/0825249/redis-returns-to-open-source-after-year-long-proprietary-detour
- Source link: https://thenewstack.io/redis-is-open-source-again/
The decision follows significant market pressure, including AWS, Google, and Oracle [3]backing the Valkey fork , which gained momentum in the open source community.
Redis believes the AGPL license provides sufficient protection from cloud providers while satisfying open source requirements. Redis 8 will incorporate vector sets and integrate previously separate Redis Stack features including JSON, Time Series, and probabilistic data support.
[1] https://thenewstack.io/redis-is-open-source-again/
[2] https://bsd.slashdot.org/story/24/03/21/225211/redis-to-adopt-source-available-licensing-starting-with-next-version
[3] https://news.slashdot.org/story/24/09/01/072220/open-source-redis-fork-valkey-has-momentum-improvements-and-speed-says-dirk-hohndel
AGPL (Score:2)
For me, the AGPL is even less usable license than the proprietary licenses.
Re: (Score:2)
Yeah, many companies will just reject any use of AGPL software out of hand. The good news is unless you're offering redis access to your customers, the general interpretation of the AGPL would mean that even if you add a plugin or something to redis you don't have to distribute the source. It also is pretty well established that having a service you rely on behind the scenes and don't modify definitely doesn't violate the license if you don't release your source. So I get the reluctance, especially from b
Re: (Score:1)
Your comment is on par with a comment only stating stating "I hate it," because you provide no rationale for your assertion. I mean, this site isn't all about you, so why would we care what your personal feelings are if you fail to include anything else?
Re: AGPL (Score:2)
Why? Most people will make no modifications to redis. It is almost always used unmodified.
Re: AGPL (Score:2)
If you use the unmodified redis library in your app running on your server... Then your app becomes AGPL as far as i understand. AGPL is based on GPL, not LGPL so there is no linker exception.
Too late (Score:5, Insightful)
While it is good that they realized the hole in the foot was self inflicted, they will never walk quite right ever again.
The large customers that Redis wanted to pay them more forked the project, and are now having their engineers (who were substantial contributors to the Redis code base previously) work on that fork instead, and have introduced a number of noticeable improvements to that code that matter to those large customers (odds are they had been using variants of those improvements internally, but now are sharing). The mindshare is now with the valkey fork, not Redis.
Redis continues to hint at an IPO real soon now. I don't think their valuation is going to be what they hoped for just a few years ago.
Trust the guy that just broke your nose (Score:4, Funny)
Here's some flowers. Please take me back, baby. Won't happen again, I promise.
Re: (Score:2)
In memory rather than a database that's stored on disk, like Postgres.
Nope. They're still screwed. (Score:1)
There's no issues staying with Valkey, and no benefit to returning to Redis even with their hurriedly added new features.
Too late (Score:2)
Too late, we already switched to Valkey
so sad.. (Score:2)
I've already moved on. Maybe I'll come back when my current solution tries to go closed source.
Undoing (Score:2)
My thoughts, they used to make money, tried to close it, found that people lost confidence in their proprietary sales and now need to get people back after all that AI investment.
Wouldn't trust them to not pull the rug again in the future.
Sorry (Score:1)
They're completely dead to me.