|
| 1 | +--- |
| 2 | +title: Valkey |
| 3 | +desc: Production-ready Valkey on Zerops platform with managed infrastructure and automatic security configuration. Deploy and run your in-memory data store with zero operational overhead. |
| 4 | +--- |
| 5 | + |
| 6 | +import UnorderedList from '@site/src/components/UnorderedList'; |
| 7 | +import UnorderedCodeList from '@site/src/components/UnorderedCodeList'; |
| 8 | +import data from '@site/static/data.json'; |
| 9 | + |
| 10 | +Valkey is a powerful, open-source alternative to Redis, offering full compatibility with Redis clients while providing an independent development path focused on community-driven innovation. Deploy and manage Valkey on Zerops' fully managed infrastructure to get instant access to high-performance in-memory data storage. |
| 11 | + |
| 12 | +:::tip |
| 13 | +Valkey is our recommended Redis alternative as KeyDB's development has slowed significantly in recent times. |
| 14 | +::: |
| 15 | + |
| 16 | +## Supported Versions |
| 17 | + |
| 18 | +Currently supported Valkey versions: |
| 19 | +<UnorderedList data={data.valkey.readable}/> |
| 20 | + |
| 21 | +Import configuration version: |
| 22 | +<UnorderedCodeList data={data.valkey.import}/> |
| 23 | + |
| 24 | +## Service Configuration |
| 25 | + |
| 26 | +Zerops offers Valkey in two deployment configurations to meet different availability requirements. |
| 27 | + |
| 28 | +## Deployment Options |
| 29 | + |
| 30 | +### Non-HA Setup |
| 31 | +- Single node deployment on port `6379` (non-TLS) and `6380` (TLS) |
| 32 | +- No backup mechanism beyond Zerops infrastructure reliability |
| 33 | +- Data persists unless the hardware node fails |
| 34 | +- Suitable for development or non-critical workloads |
| 35 | + |
| 36 | +### HA (High Availability) Setup |
| 37 | + |
| 38 | +Our HA implementation uses a unique approach to ensure high availability while maintaining compatibility with all Redis clients: |
| 39 | + |
| 40 | +- 3-node configuration (1 master + 2 replicas) |
| 41 | +- Access ports: |
| 42 | + - `6379` - read/write operations (non-TLS, routed to master) |
| 43 | + - `6380` - read/write operations over TLS (routed to master) |
| 44 | + - `7000` - read-only operations (non-TLS) |
| 45 | + - `7001` - read-only operations over TLS |
| 46 | +- Implementation details: |
| 47 | + - All nodes are configured identically and listen on standard ports |
| 48 | + - First node in the cluster is designated as the master |
| 49 | + - On replica nodes, ports `6379`/`6380` traffic is forwarded to the master |
| 50 | + - Ports `7000`/`7001` are mapped locally to each node for direct replica access |
| 51 | + - When a master fails, a replica is promoted and routing is updated automatically |
| 52 | + - DNS entries are updated for seamless client connection |
| 53 | + - This implementation provides traffic forwarding to master (not natively supported by Valkey) |
| 54 | + |
| 55 | +:::note |
| 56 | +Be aware that replica data may lag slightly behind the master due to asynchronous replication. |
| 57 | +::: |
| 58 | + |
| 59 | +## Learn More |
| 60 | + |
| 61 | +- [Official Valkey Documentation](https://valkey.io/docs) - Comprehensive guide to Valkey features |
| 62 | + |
| 63 | +## Support |
| 64 | + |
| 65 | +For advanced configurations or custom requirements: |
| 66 | +- Join our [Discord community](https://discord.gg/zerops) |
| 67 | +- Contact support via [email](mailto:support@zerops.io) |
0 commit comments