Welcome to Valkey GLIDE!

Valkey General Language Independent Driver for the Enterprise (GLIDE) is an official open-source Valkey client library, proudly part of the Valkey organization. Our mission is to make your experience with Valkey and Redis OSS seamless and enjoyable. Whether you're a seasoned developer or just starting out, Valkey GLIDE is here to support you every step of the way.

Visit our official documentation at glide.valkey.io.

Why Choose Valkey GLIDE?

• Community and Open Source: Join our vibrant community and contribute to the project. We are always here to respond, and the client is for the community.
• Reliability: Built with best practices learned from over a decade of operating Redis OSS-compatible services.
• Performance: Optimized for high performance and low latency.
• High Availability: Designed to ensure your applications are always up and running.
• Cross-Language Support: Implemented using a core driver framework written in Rust, with language-specific extensions to ensure consistency and reduce complexity.
• Stability and Fault Tolerance: We brought our years of experience to create a bulletproof client.
• Backed and Supported by AWS and GCP: Ensuring robust support and continuous improvement of the project.

Key Features

• AZ Affinity – Ensures low-latency connections and minimal cross-zone costs by routing read traffic to replicas in the clients availability zone. (Requires Valkey server version 8.0+ or AWS ElastiCache for Valkey 7.2+).
• PubSub Auto-Reconnection – Seamless background resubscription on topology updates or disconnection.
• Sharded PubSub – Native support for sharded PubSub across cluster slots.
• Cluster-Aware MGET/MSET/DEL/FLUSHALL – Execute multi-key commands across cluster slots without manual key grouping.
• Cluster Scan – Unified key iteration across shards using a consistent, high-level API for cluster environments.
• Support for TS / CJS / MJS – Fully compatible with modern and legacy JavaScript/TypeScript runtimes.
• Support for asyncio / anyio / trio – Native compatibility with modern Python async frameworks, enabling efficient and seamless integration into asynchronous workflows.
• Batching (Pipeline and Transaction) – Efficiently execute multiple commands in a single network roundtrip, significantly reducing latency and improving throughput.
• OpenTelemetry – Integrated tracing support for enhanced observability and easier debugging in distributed environments.

Supported Engine Versions

Valkey GLIDE is API-compatible with the following engine versions:

Engine Type	6.2	7.0	7.1	7.2	8.0	8.1	9.0	9.1
Valkey	-	-	-	✅	✅	✅	✅	✅
Redis	✅	✅	✅	✅	-	-	-	-

Current Status and Upcoming Releases

The client currently supports Python, Java, Node.js, Go, C#, and PHP. C# and PHP have preview releases, and have been moved to separate repositories to simplify development. Active development continues for C#, PHP, C++ and Ruby clients. Python, Java, Node.js and Go clients will be moved to separate repositories in the near future.

v2.4.0 (May 2026)

The following are some of the changes planned for 2.4.0 release:

• Client-Side Caching: for Java, Node, Go.
• Complete support for Valkey Search 1.2 and JSON module.
• Add NodeDiscoveryMode option for all languages
• Further improvements and fixes.

For the detailed list of changes, see the release page.

Other Releases

See our releases section

Getting Started

Documentation Visit our official Valkey GLIDE's documentation site.

Supported Languages

• Java
• Python
• Node
• Go
• Php

Under Development SDKs

• C#
• C++
• Ruby

General Concepts:

• Custom Command
• Connection Management
• Multi-Slot Command Handling
• Inflight Request Limit
• PubSub Support
• Cluster Scan
• Dynamic Password Management
• Modules API
• Batching (Pipeline and Transaction)
• OpenTelemetry
• Compression (EXPERIMENTAL)
• Client-Side Caching

Migration Guides

• go-redis
• ioredis
• Jedis
• Lettuce
• Redisson
• redis-py
• StackExchange.Redis
• PHPRedis

Community

• Contributors meeting

Ecosystem

Valkey GLIDE has a growing ecosystem of integrations and extensions that enhance its functionality across different frameworks and use cases:

• node-flexible-rate-limiter - A flexible rate limiting library for Node.js with Valkey GLIDE backend support
• fastify-valkey-glide - Fastify plugin for Valkey GLIDE integration, enabling seamless caching and session management
• aiocache - Python async caching framework with Valkey GLIDE backend support for high-performance distributed caching
• aws-lambda-powertools-typescript - AWS Lambda Powertools for TypeScript with Valkey GLIDE integration in the idempotency feature (more integrations planned)
• aws-lambda-powertools-python - AWS Lambda Powertools for Python with Valkey GLIDE support in the idempotency feature (more integrations planned)
• redlock-universal - Distributed lock library for Node.js with native GLIDE adapter, featuring auto-extension and atomic batch acquisition

Experimental Features

Compression (EXPERIMENTAL)

⚠️ WARNING: This feature is experimental

Valkey GLIDE supports automatic compression and decompression of string values to reduce memory usage and network bandwidth. Currently supports SET, GET, MGET, MSET, MSETNX, GETEX, GETDEL, GETSET, SETEX, PSETEX, and SETNX commands.

Incompatible Commands: Compression is NOT compatible with commands that manipulate or compare string data on the server side:

• APPEND, GETRANGE, SETRANGE, STRLEN, LCS, SUBSTR
• DELIFEQ and SET with IFEQ or IFNE
• INCR, INCRBY, INCRBYFLOAT, DECR, DECRBY
• GETBIT, SETBIT, BITCOUNT, BITPOS, BITFIELD, BITFIELD_RO, BITOP

Using these commands with compressed values will result in incorrect behavior or errors.

Getting Help

If you have any questions, feature requests, encounter issues, or need assistance with this project, please don't hesitate to open a GitHub issue. Our community and contributors are here to help you. Before creating an issue, we recommend checking the existing issues to see if your question or problem has already been addressed. If not, feel free to create a new issue, and we'll do our best to assist you. Please provide as much detail as possible in your issue description, including:

1. A clear and concise title
2. Detailed description of the problem or question
3. Reproducible test case or step-by-step instructions
4. Valkey GLIDE version in use
5. Operating system details
6. Server version
7. Cluster or standalone setup information, including topology, number of shards, number of replicas, and data types used
8. Relevant modifications you've made
9. Any unusual aspects of your environment or deployment
10. Log files

Contributing

GitHub is a platform for collaborative coding. If you're interested in writing code, we encourage you to contribute by submitting pull requests from forked copies of this repository. Additionally, please consider creating GitHub issues for reporting bugs and suggesting new features. Feel free to comment on issues that interest. For more info see Contributing.

Get Involved!

We invite you to join our open-source community and contribute to Valkey GLIDE. Whether it's reporting bugs, suggesting new features, or submitting pull requests, your contributions are highly valued. Check out our Contributing Guidelines to get started.

If you have any questions or need assistance, don't hesitate to reach out. Open a GitHub issue, and our community and contributors will be happy to help you.

Community Support and Feedback

We encourage you to join our community to support, share feedback, and ask questions. You can approach us for anything on our Valkey Slack: Join Valkey Slack.

License

• Apache License 2.0