Redis users considering alternatives after licensing move

Valkey is just the way to go. No real reasons to stay with Redis. Valkey is supported by multiple industry players and by the Linux Foundation.

They had Elastic as an example to work off of (and how badly that was received). They did it anyway. No sympathy.

&gt; Redis CEO Rowan Trollope defended his company&#x27;s move away from the more permissive interpretation of open source. He said the decision was designed to <i>prevent AWS and Google from charging for Redis</i> in their database services without paying for it.<p>This seems to be a similar reason why Elastic Search moved from open source.<p>From the founder&#x2F;CTO of Elastic:<p>I never stopped believing in Open Source. I’m going on 25 years and counting as a true believer. So why the change 3 years ago? <i>We had issues with AWS and the market confusion their offering was causing</i>. So after trying all the other options we could think of, we changed the license.<p>But who knows what the future holds? Maybe the Redis team will change their mind and revert back the decision like Elastic Search did a few weeks ago: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41394797">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41394797</a>

I guess I don&#x27;t really understand the blowback when a project tries to monetize, but not when AWS takes your free shit and monetizes it for themselves.

The article suggests valkey as an alternative with nice features in recent versions.<p>If redis finds a way to integrate these features from these other fork(s) back into its own product, adds additional &quot;enterprise&quot; feature set on top and sell it, I wonder how it will be received by the OSS community.<p>Are there any products that are importing features from their more permissive competitive forks ?

I was recently looking at keydb due to the licensing move and well I also liked the fact that the data can be encrypted at rest, but it looks like there hasn&#x27;t been any activity on the repo in 5 months, anyone familiar with it or have good alternatives there?

I&#x27;m still a bit out of the loop here. How exactly does the Redis license change affect me anyway, as an end user who just runs Redis binaries and does not use or sell any managed redis service?

Discussion from March:<p><i>Redis adopts dual source-available licensing</i><p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=39772562">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=39772562</a>

Does this move ever go well?

Can redis essentially be replaced with postgresql with unlogged tables or memcached (if you really wanted pure caching)?