Overview

The Valkey GLIDE Jedis Compatibility Layer is a drop-in replacement that enables seamless migration from Jedis to Valkey GLIDE with minimal or no code changes.

It implements the Jedis API while using the high-performance Valkey GLIDE client underneath. This allows existing Jedis applications to benefit from GLIDE’s modern architecture without a complete rewrite.

Zero-Code Migration

For applications using standard Redis commands, migration can be as simple as changing a single dependency in your build configuration. Your existing Jedis code continues to work without modification:

import redis.clients.jedis.Jedis;

// This code works unchanged with the compatibility layer
Jedis jedis = new Jedis();
jedis.set("key", "value");
String result = jedis.get("key");

Other Benefits

Reduced Effort: Eliminates the need to rewrite most application code, saving development time, reducing testing, and lowering migration risk.
Gradual Migration: Start by swapping the dependency. Later, you can incrementally migrate complex features to native GLIDE APIs at your own pace.
Business Continuity: Avoid “big-bang” rewrites. Deploy changes incrementally with minimal downtime and the ability to roll back easily.
Faster Time-to-Value: Immediately benefit from GLIDE’s modern async I/O model and optimized performance.

Limitations

The compatibility layer is essentially a wrapper around Valkey GLIDE that implements Jedis interface. As such, not all Jedis and Valkey GLIDE features are supported.

For simple applications, the wrapper maybe enough. However other applications that wants to take advantage of Valkey GLIDE features, or depends heavily on unsupported features, a full migration to the native GLIDE API is recommended.

Next Steps

Ready to get started?

Migration Instructions Step-by-step instructions for migrating using the Jedis Compatibility Layer.

Supported Features See how Jedis commands and configurations are supported.

Configuration Mapping How Jedis configurations maps to Valkey GLIDE configurations.