Trust is lost already and the damage they caused is unrecoverable. Valkey already is widely adopted and accepted as replacement.
this post was submitted on 01 May 2025
41 points (100.0% liked)
Tech
1033 readers
1 users here now
A community for high quality news and discussion around technological advancements and changes
Things that fit:
- New tech releases
- Major tech changes
- Major milestones for tech
- Major tech news such as data breaches, discontinuation
Things that don't fit
- Minor app updates
- Government legislation
- Company news
- Opinion pieces
founded 1 year ago
MODERATORS
My thoughts exactly. The news last year was what I needed to finally get off of Redis Cloud, and with AWS offering Valkey Serverless, we were able to make the costs work out to save money.
wait.. so to get this straight, you were paying Redis, a company that creates an open source project, for their offerings in order to keep funding them. When they changed their license so that their business wouldn't be cannibalized by AWS (who was modifying Redis under the hood, not contributing it back to the community, and then pricing it lower) instead of continuing to pay Redis who's license change wouldn't have affected you at all, you instead started paying AWS for a project they started in order to avoid paying for open source code they were using.
you do realize this is a walmart situation right?
Yup, that's pretty much right. TBH, the Redis Cloud costs were pretty exorbitant for the tier we were on before the changes, and there had been internal discussion on moving away from them. AWS Valkey Serverless offering is significantly less expensive for the workload we needed across the hosted options, it didn't make sense to continue paying double for Redis Cloud. If Redis' goal with the license change was to get AWS to make it's own thing, then I guess mission accomplished, but they threw the baby out with the bathwater IMO. Developers have jumped to Valkey, and it will take time to win them back, if that's possible.
you do realize this is a walmart situation right?
You do realize that it was an open-source project that went full-on closed source evil corporation, right?
No it wasn’t. Their license was completely to prevent corporations like Amazon from sucking open source dry. Like they said, they hoped OSI would recognize it as an open source license.
they hoped OSI would recognize it as an open source license
If they wanted the OSI to recognize it as open source license, why didn’t they request a review?
So, he says that the AGPL only really applies to Amazon and Google. Because they are cloud providers presumably, which means it also applies to Alibaba and Oracle. And Microsoft.
Guess who contributes code? That’s right, same list.
What is the incentive for these companies to switch back to Redis when Valkey is available as BSD? They can all collaborate on Valkey and ignore Redis all together.
Are the users going to flock to AGPL instead of the BSD version? I doubt it.
Too little too late
rofl redis is dumb as fuck. valkey is already faster
I guess I'm glad to see more use of AGPL. Maybe that will make other projects less reticent to touch AGPL with a 10-foot pole. That could be a tiny silver lining out of this whole mess.
...and everyone suddenly trusted them again?
Redis stands for redistribute
right?