data-storage / cli
Dragonfly
Capability: Dragonfly
Use it when
- A single-threaded Redis instance is CPU-bound on one core and cannot use the rest of the machine
- Cache memory use spikes to multiples of the dataset during BGSAVE snapshots and risks OOM
What it solves
Not the fit when
- Primary durable database-of-record workloads without separately validating persistence and recovery requirements
- Assuming complete compatibility with every current Redis command or behavior; the README describes roughly Redis 5.0 API coverage
- TTL deadlines beyond about eight years or exact millisecond precision for long deadlines
- Exposing the built-in HTTP admin console to untrusted networks
- Providing Dragonfly or a substantial set of its functionality as a hosted or managed service under the current BSL 1.1 Additional Use Grant; affected uses require a commercial license or waiting for the applicable change license/date
- persistent relational storage with joins
- full-text search ranking
- durable system of record with cross-region replication
Install
Download the dragonfly release binary (e.g. dragonfly-x86_64) from GitHub releases or run the Docker image; see the Quick Start in docs/quick-start
Invoke
./dragonfly-x86_64 --logtostderr --requirepass=yourpass --cache_mode=true --maxmemory=12gb --bind localhost --port 6379, then connect with any Redis or Memcached client; Prometheus metrics at :6379/metrics
Alternatives
No reviewed alternatives recorded yet.