drakeydb is a fork of DragonflyDB that ports KeyDB-style active-replica / multi-master replication onto Dragonfly's modern, multi-threaded, shared-nothing architecture.
Dragonfly's performance. KeyDB's active-active topology.
Early development. The fork tracks upstream dragonflydb/dragonfly continuously; multi-master
support is being built in phases:
| Phase | Feature | Status |
|---|---|---|
| 0 | Fork setup + rebrand (binary: drakeydb) |
complete |
| 1 | Persistent node identity (UUID) + handshake | complete |
| 2 | Writable multi-source replica (fan-in) | complete |
| 3 | Origin-tagged journal + active-active mesh | complete |
| 4–6 | MVCC timestamps + convergent last-write-wins (streaming + full-sync merge) | complete (the full-sync merge and the streaming guard both landed within phase 4) |
| 7 | One-way onboarding from live KeyDB masters | in progress |
| 8–9 | Mesh hardening, CI, first release | planned |
With multi-master flags off, drakeydb retains wire protocol, on-disk format, metrics, and
INFO compatibility with upstream Dragonfly. Runtime defaults and fork-specific surface
behavior can differ; see BRANDING.md for the compatibility policy.
The multi-master interface is implemented (phases 2–4). For merge, tombstone, and operational guidance see docs/multi-master.md. For example:
# Node A and node B, both writable, replicating from each other (full mesh):
drakeydb --active_replica --multi_master --port 6379 # on node A
drakeydb --active_replica --multi_master --port 6379 # on node B
redis-cli -h nodeA replicaof nodeB 6379
redis-cli -h nodeB replicaof nodeA 6379Conflicts on state-carrying commands (SET, DEL, EXPIRE, …) resolve by per-key
last-write-wins MVCC timestamps. NTP-synchronized clocks are a hard requirement for
multi-master deployments.
Identical to upstream Dragonfly — see docs/build-from-source.md.
git clone --recursive https://github.com/darkspadez/drakeydb
cd drakeydb
./helio/blaze.sh -release
cd build-opt && ninja dragonfly # CMake target keeps the upstream name...
./drakeydb --alsologtostderr # ...the binary is drakeydbLinux is the primary platform (kernel 5.11+ recommended for io_uring). On macOS, build and run inside a Linux container.
drakeydb deliberately renames only the surface: the binary, docs, and packaging. Internal
namespaces, the DFLY command family, replication wire tokens, RDB format markers, Prometheus
metric names, and the dragonfly_version INFO field all stay unchanged for ecosystem
compatibility and to keep upstream merges cheap. See BRANDING.md for the full
policy and docs/UPSTREAM-SYNC.md for how upstream patches are merged.
drakeydb inherits Dragonfly's Business Source License 1.1. It converts to Apache 2.0 on Nov 1, 2030, or on the fourth anniversary of the first public distribution of a specific version, whichever comes first. The Additional Use Grant permits use only as part of your own product or service when it is not an in-memory data store product or service, and prohibits using, providing, distributing, or making the Licensed Work available as a Service to third parties. See LICENSE.md for the complete applicable terms. Ported KeyDB logic is BSD-3-Clause; see NOTICE for attributions.
- The DragonflyDB team — the fastest in-memory store engine there is.
- KeyDB by EQ Alpha Technology / Snap Inc. — the active-replication design this fork ports.