Go-Redis replacement valkey-go or valkey-glide ?

[royatanu94]

Hello,
We are currently using go-redis to communicate with valkey.
We want to migrate go-redis with the options provided by valkey.
I am not getting should we go for valkey-go or valkey-glide ?
Please help to understand the difference between valkey-go and valkey-glide.

Also please suggest if there is any migration doc available from go-redis to valkey-go.

TIA

[yipin-chen]

Valkey-GO (https://github.com/valkey-io/valkey-go)
Valkey-GO is a Go-specific client library for the Valkey, and it is a fork of the rueidis Go client (https://github.com/redis/rueidis) that does auto pipelining and supports server-assisted client-side caching. The list of features and example code can be found in its README.

Valkey-GLIDE (https://github.com/valkey-io/valkey-glide)
Valkey-GLIDE (General Language Independent Driver for the Enterprise) is implemented using a core driver framework written in Rust, with language-specific extensions to ensure consistency and reduce complexity. In addition to Java, Python, Node.js, Valkey-GLIDE adds the support in Go in Release 2.0. Active development continues for C#, C++, and Ruby clients. The list of features can be found in its README. The example code can be found here.

Here are few key differences:

Valkey-GO:

• Sync API
• Valkey-GO specific features: (Feature Comparison Table can be found here)
  • Client Side Caching
  • Persistent Connection Pool
• Supported module commands
• Supported Go-Redis like API via valkeycompat
• Low-level, raw commands interface
• Support all Go platforms

Valkey-GLIDE:

• Async API for all clients except GO, which is Sync API
• Valkey-GLIDE specific features: (Feature Comparison Table can be found here)
  • Cluster Scan
  • Open Telemetry
  • Multiplex Connection Management
  • Automatic Topology Tracking
• Go client currently doesn’t support module commands
• Plan to add a compatibility layer to the Go client in the future
• Support low-level interface and high-level features & abstractions, such as cluster auto-rebalancing, auto-reconnecting, error handling, and observability support
• Platform dependent on Linux (Ubuntu 20, Amazon Linux 2) and MacOS (aarch_64 and amd64)