Our great sponsors
| KeyDB | edis | |
|---|---|---|
| 24 | 2 | |
| 10,680 | 468 | |
| 19.0% | - | |
| 8.4 | 0.0 | |
| 13 days ago | over 8 years ago | |
| C++ | Erlang | |
| BSD 3-clause "New" or "Revised" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
KeyDB
-
Redict 7.3.0, a copyleft fork of Redis, is now available
Three. KeyDB forked before the recent shake-up.
https://github.com/Snapchat/KeyDB
-
KeyDB: A Multithreaded Fork of Redis
Can you explain what lead you to believe it's dead?
Looking at the Issues in their Github, a couple of days ago they mentioned to be working on some features in a branch.
https://github.com/Snapchat/KeyDB/issues/798#issuecomment-20...
-
Redict is an independent, copyleft fork of Redis
https://github.com/Snapchat/KeyDB
KeyDB is an existing fork that’s well supported and has a solid community for those interested. It takes a different philosophy to Redis but can be a drop in replacement in many cases
- KeyDB – A Multithreaded Fork of Redis
- Redis License Changed
- [BUG] Address is used after it has been freed (dict).
-
The first version of Redis, written in Tcl
To me it's still not clear if 6.3.x is stable (https://github.com/Snapchat/KeyDB/issues/494) and performant (https://github.com/Snapchat/KeyDB/issues/470).
-
Migrating from Redis to KeyDB
I posted about KeyDB, a multi-threaded fork of Redis, here already a while ago. We still use it in some cases and find it beneficial.
- Snapchat/KeyDB: A Multithreaded Fork of Redis
edis
- Edis: An Erlang Implementation of Redis
-
KeyDB CEO Interview: Getting into YC with a Fork of Redis
We (me and some folks at my old consultancy) wrote an Erlang version of Redis (https://github.com/cbd/edis) for some of the same reasons - multithreading changes some of the scaling semantics in interesting ways. It was mostly for fun but ended up in some real projects as a simple REDIS protocol implementation front-end where the backend could be replaced with whatever the implementor wants.
What are some alternatives?
dragonfly - A modern replacement for Redis and Memcached
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
keydb-operator - A KeyDB (Drop-In Alternative to Redis) Operator for Kubernetes, based on Ansible Operator SDK.
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
raids - Cache distribution services: http, websock, redis, memcached
tikv - Distributed transactional key-value database, originally created to complement TiDB
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.
skytable - Skytable is a modern scalable NoSQL database with BlueQL, designed for performance, scalability and flexibility. Skytable gives you spaces, models, data types, complex collections and more to build powerful experiences
dynomite - A generic dynamo implementation for different k-v storage engines