Redict is deprecated

60 points by val 10 hours ago on lobsters | 9 comments

ema-pe | 5 hours ago

I mean, from what I observed years ago, Redict aimed to stay mostly compatible with Redis, while the other fork Valkey aims to continue and extend Redis with new functionality as well. But since Redis is back to being OSS, why would anyone choose Redict?

chrismorgan | 5 hours ago

why would anyone choose Redict?

The post answered that:

We advise against switching back to Redis; though it is once again open source, and copyleft, it uses a contributor license agreement which will facilitate another rug-pull when Redis has a bad financial quarter.

ema-pe | 4 hours ago

I'm not sure about that. The main reason Redis went back to being OSS is antirez. And I hope Redis Labs learned from its mistake, though I'm a bit pessimistic about that.

gcupc | 5 hours ago

Honestly, I was mildly surprised when Redict was stared, given valkey was already pretty successful at the time.

[OP] val | 2 hours ago

Redict was actually started just before Valkey. Its first commit was on 2024-03-21 while Valkey's was on 2024-03-22 and got its name on 2023-03-28

Ah, I was mistaken, then. I must not have heard about Redict until quite a bit later.

tedchs | 4 hours ago

Personally, when antirez left Redis Labs, I lost any motivation for paying for their specific cloud hosting above the many competitors. I presume I wasn't the only one.

legoktm | 3 hours ago

I came to the same conclusion myself about a month ago. However:

If you use containers, simply pull the valkey container instead and ensure that it runs with the appropriate config file.

This was not the case for me, the RDB formats were incompatible so I had to remove the old one and let valkey create a new one from scratch. That was totally fine since I was using it as a ephemeral cache.

xyproto | 4 hours ago

Redict is dead. Long live Valkey.