Redis is no longer open source

Redis is no longer open source. The wildly popular Key-Value Database announced that future versions will be distributed under new licenses. Which restricts how you can use the software. The change primarily targets hosting providers like AWS. who will no longer be able to provide managed Redis services without paying a license fee to Redis.
If you're using Redis in your stack you should take a look at the new terms and probably look for alternatives for your next project.

[@AbbyChau]

Why alternatives? The license is super fair to anyone. You should blame more on those blood sucking cloud SaaS who take Redis as their own services.

[@vickylance]

AWS is not the only Cloud Saas. There are many small business that has cloud offering that is based on Redis and this basically kills them

[@bufferhead_]

The licenses they chosen will scare a lot of people away. SSLP basically forces you to open source everything and RSALv2 is very vague. I won’t use Redis anymore, it’s just to much risk in a commercial product and I’m sure some of the alternatives will gain a lot of popularity right now. Not defending AWS but I don’t think this will hurt them. They will either fork the project or build their own Redis compatible version.

[@AbbyChau]

​@@bufferhead_ nope , you only need to opensource if you embed redis in your product. it is the same as all GPL licenses and RSAL protects Redis from non-free SaaSs like AWS/Azure/etc... looks super fair to me. and i love how Redis change their way. I were already using stuffs like keydb and other MIT based alts but this redis's move actually in contrast makes me wants to support it back.

[@AbbyChau]

@@vickylance they are bad too, not only AWS. size does not matter.

[@AbbyChau]

​@@bufferhead_
1. The licenses they chosen will scare a lot of people away.
> So. do they have any valid arguments?
2. SSPL basically forces you to open source everything and RSALv2 is very vague.
> RSAL protects Redis from non-free SaaSs like AWS/Azure/etc... looks super fair to me. I love how Redis change their way.
> SSPL, which is a new concept and licensing. The core argement changes here. in short: you need to opensource if you modified redis and provide it as a service. I meant, why not? If one thinks GPL is a valid licensing, then why providing an API service which is the same as the original one is not a re-distrubution nowadays? it is just the border of API and ABI.
3. I won’t use Redis anymore, it’s just to much risk in a commercial product and I’m sure some of the alternatives will gain a lot of popularity right now.
> Specify "Risks". I were already using stuffs like keydb and other MIT based alts. Of course I won't drop them but this redis's move makes me supports Redis more because of its sanity.
> Don't make BSD/MIT license a feat. that everyone needs to compete for. GPLv3 and no-service wrapping is very good to protect the interest of the original developers / company. I feel sick of ppl just keep thinking "how to make money from using other ppl's open source softwares" everyday.
I may not be tight with the Redis community but I know many small bits of Redis's architecture itself. it is kind of weak and simple without Redis Stack and I doubt if it is a good time to lock-in the profit now.
However, I support how OSS devs protects themselve from blood-sucking firms like AWS/Azure/GCP away.