What maps to what: migrate from Dragonfly 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
| Dragonfly | KiviDB |
|---|---|
proactor_threads | Not needed: commands run on every core. --threads sets the worker count |
| Strings, lists, sets, sorted sets, hashes, streams, bitmaps, geo, HyperLogLog, JSON | The same |
HSETEX, FIELDEXPIRE (expiry of one hash field) | HSETEX with EX, HEXPIRE, HPEXPIRE: Redis 7.4/8 syntax, which differs from Dragonfly's |
SADDEX (expiry of one set member) | No equivalent |
FIELDTTL | HTTL, HPTTL |
Snapshots in .dfs files (the default) | Not readable by KiviDB. Use SAVE RDB |
| Replication to Dragonfly replicas | Not to KiviDB: Dragonfly answers PSYNC with unknown command |
MIGRATE | Dragonfly has no MIGRATE |
| Keyspace notifications: expiry events only | All events |
Search (FT.*), Bloom filters (BF.*) | Search is built in (run FT.CREATE again). Bloom filters: not supported |
| Lua scripts | 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 |
Emulated cluster mode (--cluster_mode=emulated) | A real cluster (--cluster-enabled yes), or one server |
| Default port 6379 | 6380 (KiviDB Cloud: 6379, or 6380 with TLS) |