Migrate from Redis to ValKey or KeyDB

[caniko]

Redis performed a rug pull on its FOSS community. You should either switch to ValKey if you want feature parity with Redis, or move to KeyDB the Snapchat fork that makes Redis multithreaded.

[bo0tzz]

We're planning to remove redis in favour of using postgres for the queues, so we won't be putting any effort into migrating to alternatives.

[OnixGH]

But according to your cursed knowledge you moved back to redis?
#10801

[caniko]

For a queue, maybe NATS is the way to go?

[alextran1502]

Since Redis has always been in the stack, we are reusing the piece until we have a better solution

[caniko]

Did you consider NATS though @alextran1502 ?

[alextran1502]

No I did not, we want to reduce the deployment setup 😅

…

On Thu, Jul 11, 2024 at 12:29 AM Can H. Tartanoglu ***@***.***> wrote: Did you consider NATS though @alextran1502 <https://github.com/alextran1502> ? — Reply to this email directly, view it on GitHub <#10087 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGONL7TLXOMGFMVOOURYLKTZLYJ2FAVCNFSM6AAAAABJC2JMNKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMBRGY4DQNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zatricky]

Just adding some data here ; For a while I'd been running with eqalpha/keydb as a drop-in replacement with no visible issues. I've switched to valkey/valkey now because I was concerned that that keydb image on dockerhub was not updated in over 10 months. Valkey appears to work fine as a drop-in replacement too.