What maps to what: migrate from KeyDB 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

KeyDBKiviDB
server-threadsNot needed: commands run on every core. --threads sets the worker count (default: cores − 2)
Strings, lists, sets, sorted sets, hashes, streams, bitmaps, geo, HyperLogLogThe same
EXPIREMEMBER, EXPIREMEMBERAT, PEXPIREMEMBERAT (expiry of one set member, hash field or sorted-set member)Hash fields: HEXPIRE, HPEXPIRE, HEXPIREAT. Set and sorted-set members: no equivalent. Subkey expiry does not come across; see gotchas
active-replica yes (two writable servers replicating to each other)No equivalent. One writable primary with read-only replicas, or a cluster
multi-master yes (one replica of several masters)No equivalent
FLASH (storage-provider flash)No equivalent: KiviDB keeps the dataset in memory, with an AOF and snapshots on disk
KEYDB.CRON, KEYDB.MEXISTS, KEYDB.HRENAME, KEYDB.NHGET and other KEYDB.* commandsNo equivalent
Lua scriptsThe lua and full builds; a switch when you create a KiviDB Cloud database
TLSThe tls and full builds; on or required per database on KiviDB Cloud
Modules (loadmodule)Not supported. Search, JSON, time series and vectors are built in
SentinelNot implemented
ClusterThe same 16,384 hash slots and CLUSTER commands; KiviDB nodes cluster only with KiviDB nodes
Default port 63796380 (KiviDB Cloud: 6379, or 6380 with TLS)