What maps to what: migrate from Valkey to KiviDB
What maps to what. Migrate to KiviDB: Move from Redis, Valkey, ElastiCache, Redis Cloud, Aiven, Aerospike, Hazelcast and more: getting the data out, loading i
| Valkey | KiviDB |
|---|---|
io-threads | Not needed: commands run on every core. --threads sets the worker count. io-threads in a config file is accepted and does nothing |
| Strings, lists, sets, sorted sets, hashes, streams, bitmaps, geo, HyperLogLog | The same |
Hash field expiry (9.0+: HEXPIRE, HSETEX, HGETEX, HTTL) | The same commands, Redis 8 syntax |
| Numbered databases in cluster mode (9.0+) | Database 0 only in cluster mode |
valkey-search, valkey-json, valkey-bloom modules | Search and JSON are built in; run FT.CREATE again. Bloom filters: not supported |
Lua scripts, FUNCTION | The lua and full builds; a switch when you create a KiviDB Cloud database |
| TLS | The tls and full builds; on or required per database on KiviDB Cloud |
| ACL users | The same ACL rules; KiviDB Cloud: users in the console |
Sentinel (valkey-sentinel) | Not implemented. See the Redis guide |
| Cluster (16,384 slots) | The same slots and CLUSTER commands; KiviDB nodes cluster only with KiviDB nodes |
| Default port 6379 | 6380 (KiviDB Cloud: 6379, or 6380 with TLS) |