Since the fork, Valkey and Redis have been diverging, especially with the latest releases - new features like COMMANDLOG, per-slot metrics, and different optimization paths. Existing Redis extensions might connect to Valkey, but there's nothing built specifically for it.
I started the first Valkey-focused VS Code extension (search "valkey" in the marketplace - only result). Features: multi-connection management, key browser, CRUD for common data types (string, hash, list, set, sorted set), and an integrated CLI.
MIT licensed, contributions welcome: https://github.com/BetterDB-inc/vscode
Also Redis now includes the new Vector Sets data type that is not part of ValKey, and I'm right now working to a new data type that is not a niche use case as Vector Sets. So I expect them to diverge even more in the near future, and that certain use cases based on Redis or ValKey will be impossible to port easily to the other fork. But I believe this was unavoidable.
I remember Vector Sets - I helped Rowan with the vector-sets-browser. Exciting to see you back working on Redis. Would love to hear more about the new data type when you can share.
And yes, it is normal for different projects to take on different paths. All the more reason for specific tooling for both as well. I am trying to keep everything Redis compatible as much as possible too.
They're still wire-compatible for core commands, so most existing code works with both. The main differences so far:
- New features diverging: Valkey added COMMANDLOG for query analysis, per-slot cluster metrics. Redis just shipped Vector Sets for similarity search.
- As antirez mentioned, this gap will keep widening
For now you can use either interchangeably for most workloads, but that window is closing.
Comment:
Since the fork, Valkey and Redis have been diverging, especially with the latest releases - new features like COMMANDLOG, per-slot metrics, and different optimization paths. Existing Redis extensions might connect to Valkey, but there's nothing built specifically for it. I started the first Valkey-focused VS Code extension (search "valkey" in the marketplace - only result). Features: multi-connection management, key browser, CRUD for common data types (string, hash, list, set, sorted set), and an integrated CLI. MIT licensed, contributions welcome: https://github.com/BetterDB-inc/vscode
Also Redis now includes the new Vector Sets data type that is not part of ValKey, and I'm right now working to a new data type that is not a niche use case as Vector Sets. So I expect them to diverge even more in the near future, and that certain use cases based on Redis or ValKey will be impossible to port easily to the other fork. But I believe this was unavoidable.
I remember Vector Sets - I helped Rowan with the vector-sets-browser. Exciting to see you back working on Redis. Would love to hear more about the new data type when you can share. And yes, it is normal for different projects to take on different paths. All the more reason for specific tooling for both as well. I am trying to keep everything Redis compatible as much as possible too.
Thanks for your efforts!
This is an interesting extension! I thought Redis and Valkey were compatible, but what are the differences between them?
They're still wire-compatible for core commands, so most existing code works with both. The main differences so far: - New features diverging: Valkey added COMMANDLOG for query analysis, per-slot cluster metrics. Redis just shipped Vector Sets for similarity search. - As antirez mentioned, this gap will keep widening For now you can use either interchangeably for most workloads, but that window is closing.
Got it, thanks! Good to know they're still compatible for now. I'll have to watch how the feature gap develops.