-
Notifications
You must be signed in to change notification settings - Fork 66
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
🚀 [Feature]: Implement Valkey Storage #1361
Comments
@H0llyW00dzZ The Redis and Rueidis clients work with Valkey. Therr's no need for anlther driver.
The valkey-go is a fork of rueidis which we have a storage driver for. |
However, that might not work anymore in the future. |
I think we are at a good point to revisit this issue. According to a December 2024 Redis Blog Post:
In this case, it may make sense to officially support Valkey through a separate storage driver. If we do this, we don't need to worry as much about breaking changes between Redis/Rueidis clients and Valkey clients for users that rely on GoFiber's storage module. Currently, the Valkey client appears to be just enough of the same as Ruedis, so it could be as simple as a copy-and-paste of the existing driver and rename to use Valkey's syntax. This way, once the clients start to vastly diverge, it won't inadvertently break GoFiber applications that upgrade to a future version. What do you all think of this? |
@grivera64 Agree, the code from the |
Feature Description
This is similar to the Redis link
here
Additional Context (optional)
No response
Code Snippet (optional)
No response
Checklist:
The text was updated successfully, but these errors were encountered: