-
Notifications
You must be signed in to change notification settings - Fork 71
Implement valkey backend #460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Implement valkey backend #460
Conversation
f20d64a to
96a6b63
Compare
|
Before I undraft this, I will attempt to run this in a private project to see if I missed anything. The queue tests should cover the majority and they seem to work fine, but there are some key differences inside Dequeue and Size that I'm not entirely sure of. |
38ef7ff to
3a48b8e
Compare
e63ccd8 to
4fafa8c
Compare
|
re-authored all commits to stop using my other git account :) |
…er-mode)" This reverts commit 534b23f.
…when no instance is found in the workflow
c7c2148 to
f85e196
Compare
|
To sum up, this is basically a carbon copy of the Redis backend implementation. I've actually tested the Redis backend with a Valkey server, and it actually works as far as I can see. But obviously, guaranteeing that compatibility might not hold forever. Hence, a valkey-go SDK implementation to go alongside the Redis variant. |
|
@cschleiden could I get your eyes on this please? :) |
implements #363