←back to thread

82 points lsferreira42 | 6 comments | | HN request time: 0.001s | source | bottom
Show context
untech ◴[] No.42202229[source]
I thought people stopped using Redis and moved on to a fork because of licensing issues. Is this true?
replies(4): >>42202334 #>>42202507 #>>42202663 #>>42203038 #
1. silverwind ◴[] No.42202507[source]
Only AWS did, and their fork is already lacking several important new features like HEXPIRE.
replies(2): >>42202598 #>>42207384 #
2. slig ◴[] No.42202598[source]
>`HEXPIRE`

Finally. Hope they implement this soon at Valkey.

replies(1): >>42207357 #
3. reconditerose ◴[] No.42207357[source]
We're working on it, you can follow the progress here: https://github.com/valkey-io/valkey/issues/640.
replies(2): >>42212169 #>>42213715 #
4. reconditerose ◴[] No.42207384[source]
There is a lot of adoption of Valkey. I know it's fun to hate on AWS, but there is a wider shift than just them.

https://cloud.google.com/blog/products/databases/announcing-... https://upcloud.com/blog/now-supporting-valkey https://aiven.io/blog/introducing-aiven-for-valkey https://www.instaclustr.com/blog/valkey-now-available/ https://elest.io/open-source/valkey

5. slig ◴[] No.42212169{3}[source]
Great, thank you so much!
6. OPoncz ◴[] No.42213715{3}[source]
Its available on Dragonfly https://github.com/dragonflydb/dragonfly

Here is the docs https://www.dragonflydb.io/docs/command-reference/hashes/hex...