Skip to content
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

Support Plan for Valkey #3225

Open
jonathannaguin opened this issue Mar 24, 2025 · 4 comments
Open

Support Plan for Valkey #3225

jonathannaguin opened this issue Mar 24, 2025 · 4 comments
Labels
status: waiting-for-feedback We need additional information before we can continue

Comments

@jonathannaguin
Copy link

Hello,

We are considering on using Lettuce for connecting to a Valkey server (AWS ElasticCache) and even though we can choose to use Valkey 7.x for increased compatibility, we are wondering which version of Valkey is really supported by Lettuce. And whatever plans you may have for Valkey 8.x.

Thanks!

@tishun
Copy link
Collaborator

tishun commented Mar 24, 2025

To our knowledge, Redis and Valkey did not yet diverge, at least not in core data structures. Lettuce is only tested with Redis, but we do not expect incompatibilities for the standard core commands. So, there are no real plans for Valkey in general.

Lettuce will add support to the Redis Query Engine in the near future to support Redis CE search, vector search, and the rest of the capabilities (Lettuce already supports the JSON data type).

@tishun
Copy link
Collaborator

tishun commented Mar 25, 2025

Does this help?

@tishun tishun added the status: waiting-for-feedback We need additional information before we can continue label Mar 25, 2025
@jonathannaguin
Copy link
Author

Thanks @tishun, I understand your comment, still the concern we have is that Valkey will eventually diverge and more vendors are moving to Valkey due to the licensing change (AWS in our case). We could rely in our tests to ensure the library keeps been functional but without any assurance from the library itself we will likely need to consider another library.

Hope I am making sense, this Valkey/Redis topic is not that easy to follow :)

@tishun
Copy link
Collaborator

tishun commented Mar 25, 2025

To be absolutely fair we can't guarantee that there would not be - eventually - some differences between Redis and Valkey. As of right now there are several other forks or rewrites that use the same protocol, but do not share the same exact behaviour (set of commands, response signatures, etc.). We can only guarantee operational compatibility with Redis, although this is an open source project and we will always accept meaningful contributions from the community (that could bridge the gap - if there is any).

IMHO it really depends how you would end up using the driver and in most cases there shouldn't be issues, but ultimately it is up to you to choose the right tooling for your business needs.

If you need some specific details based on your use case - please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-feedback We need additional information before we can continue
Projects
None yet
Development

No branches or pull requests

2 participants