Installer keydb avec Homebrew, apk, dnf

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• keydb-benchmark
• keydb-check-aof
• keydb-check-rdb
• keydb-cli
• keydb-sentinel
• keydb-server

Historique du projet

KeyDB started in early 2019 as an experiment to add multithreading support to Redis. Its maintainers turned that experiment into an open-source database with active replication, FLASH storage, subkey expiry, and MVCC features layered onto Redis-compatible commands, modules, transactions, and scripts.

The project joined Snap in May 2022. The announcement said Snap gave KeyDB a long-term home and merged the previously Enterprise codebase into one BSD-3-Clause open-source project.

Historique d'adoption

KeyDB grew by appealing to Redis operators who wanted more throughput per node without forcing every deployment into sharding. The 2022 Snap announcement said the project had passed 3 million downloads since launch, showing adoption beyond a small fork experiment.

Modes d'utilisation

Users deploy KeyDB as a Redis-compatible server, often testing it where single-node Redis CPU limits, active-active replication, or non-blocking scan behavior matter. The command-line package includes server, CLI, benchmark, sentinel, and database-check utilities mirroring familiar Redis operational workflows.

Pourquoi les passionnés de paquets s'y intéressent

KeyDB is a classic package-manager fork story: same protocol and much of the same operational muscle memory, but a different performance architecture and governance path. For maintainers it also intersects with Redis-compatible alternatives such as Valkey, Dragonfly, and Redict after Redis licensing and ecosystem changes made fork lineage especially visible.

Chronologie

• 2019: KeyDB began as an experiment to add multithreading support to Redis.
• 2019-08: KeyDB documentation described active replication for read/write replicas and simpler failover setups.
• 2019-10: KeyDB published benchmark-oriented documentation presenting it as a multithreaded Redis fork.
• 2022-05-12: KeyDB joined Snap and consolidated enterprise features into the BSD-licensed open-source project.
• 2024: Redis-compatible forks and alternatives became more prominent after Redis licensing changes, making KeyDB part of a broader replacement discussion.

Related projects

• KeyDB is directly related to Redis, Redis Sentinel, Redis Cluster, Valkey, Dragonfly, and Redict. Its differentiators are multithreaded execution, active replication, MVCC-assisted scans, and compatibility with Redis clients and modules.

Sources

• https://docs.keydb.dev/blog/2019/10/07/blog-post/
• https://docs.keydb.dev/docs
• https://docs.keydb.dev/docs/active-rep/
• https://docs.keydb.dev/docs/mvcc/
• https://docs.keydb.dev/news/2022/05/12/keydb-joins-snap/
• https://github.com/Snapchat/KeyDB