Hacker News new | past | comments | ask | show | jobs | submit login

It is unfortunately not failing them ("unfortunately" because I very much dislike the path they took). They lost Heroku, which also didn't pay them before the license change, but they got others. I don't know if the information is public.



I'm torn on the moral issues of the re-licensing, but I'm firmly happy about the practical implications. Redis vs. Valkey is as competitive as it gets, since users can switch between the two so seamlessly (for now, at least). That's good for the industry. I expect to see a flurry of improvements to both in the coming years as they try to come out on top (some may be redundant, but I nonetheless think the pace will be faster).


Yeah, I guess I'm speaking from a sample size of 1 here since they don't share this information (and I'm too lazy to look around at what other cloud vendors are doing i.r.t. Valkey vs Reddit).

What "others" did they get, that you're aware of?


* Google added support to Valkey: https://cloud.google.com/memorystore

* AWS says they are moving: https://aws.amazon.com/blogs/opensource/why-aws-supports-val...

* Aiven added Valkey: https://aiven.io/blog/introducing-aiven-for-valkey

* Instaclustr mentioned moving: https://www.instaclustr.com/blog/redis-to-valkey/

* Oracle indicated support: https://blogs.oracle.com/cloud-infrastructure/post/oracle-su...

Azure is the main one sticking with Redis: https://azure.microsoft.com/de-de/blog/redis-license-update-...

I might edit this if I remember some more.


The azure post is very hand wavy, and it looks like azure isn’t even supporting redis 7, let alone redis minor version after the license change.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: