Engula is designed as a "drop-in" replacement for Valkey/Redis 7.2, with the goal of letting applications and client libraries connect seamlessly without breaking Redis ecosystem interoperability. This guide explains to developers what compatibility means, the range of verified clients, and how to ensure consistent behavior after migration.
Engula closely aligns with the semantics and behavior of Valkey/Redis 7.2, including:
Any observable differences are documented and, where feasible, fixed for compatibility to guarantee predictable Redis behavior consistency.
Because Engula aligns with the protocol and API of Valkey/Redis 7.2, any client that supports Redis OSS 7.2 or Valkey 7.2 and above can generally interoperate directly with Engula.
These directories list the mainstream clients for each language along with their feature support (for example, read-from-replica, smart backoff, client-side caching, etc.). As long as a client can correctly connect to Valkey or Redis 7.2, it can usually connect to Engula in the same way.
Engula supports the advanced client behaviors defined by Valkey/Redis 7.2. As long as you use standard protocol commands, the following capabilities generally interoperate:
Tip: Some features require enabling a configuration or runtime switch on the client side. Refer to the documentation of your specific client for setup; Engula provides the corresponding server-side capability support.
Engula continuously verifies compatibility with mainstream Redis/Valkey clients in its CI pipeline. Although almost all Redis/Valkey 7.2-compatible clients should work, the following clients have been explicitly verified:
| Language | Commonly Verified Clients |
|---|---|
| Go | go-redis, valkey-go |
| Java | jedis, valkey-java, redisson |
| JavaScript / TypeScript | node-redis, iovalkey |
| Python | redis-py, valkey-py |
| PHP | phpredis, predis |
If the client you use is not on the list but claims to support Valkey/Redis 7.2, it should generally work as well. If you encounter unexpected behavior, please report it to us so we can evaluate it and add it to the verification coverage set.
Migrating from Valkey/Redis 7.2 to Engula is generally very straightforward:
Engula performs automated compatibility verification against mainstream Redis client SDKs, covering:
For more information:
The Engula team continuously improves the test suite to detect and fix differences in a timely manner. Community contributions and PRs to expand coverage are welcome.
If you encounter abnormal client behavior or differences in protocol handling:
In one sentence: If it runs on Valkey or Redis 7.2, it runs on Engula. Pick your preferred client from the official Valkey/Redis client directory and seamlessly use Engula's high-performance, memory-efficient architecture.