this post was submitted on 01 May 2025
42 points (100.0% liked)

Tech

1038 readers
123 users here now

A community for high quality news and discussion around technological advancements and changes

Things that fit:

Things that don't fit

Community Wiki

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Dirk@lemmy.ml 25 points 1 week ago (1 children)

Trust is lost already and the damage they caused is unrecoverable. Valkey already is widely adopted and accepted as replacement.

[–] bamboo@lemmy.blahaj.zone 8 points 1 week ago (1 children)

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.

[–] tyler@programming.dev 11 points 1 week ago (2 children)

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?

[–] bamboo@lemmy.blahaj.zone 5 points 1 week ago

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.

[–] Dirk@lemmy.ml 2 points 1 week ago (1 children)

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?

[–] tyler@programming.dev 1 points 6 days ago (1 children)

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.

[–] Dirk@lemmy.ml 1 points 6 days ago

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?

https://opensource.org/licenses/review-process