1store
KeyDB
| 1store | KeyDB | |
|---|---|---|
| 2 | 24 | |
| 1,307 | 10,680 | |
| - | 8.0% | |
| 10.0 | 8.4 | |
| over 4 years ago | 15 days ago | |
| C++ | C++ | |
| GNU Affero General Public License v3.0 | BSD 3-clause "New" or "Revised" License |
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.
1store
-
So, you call yourself the fastest key/value store? It's 5X, 10x and 25X faster
How about including Pedis in this? It is a Redis partial reimplementation, written around Seastar: https://github.com/fastio/1store
-
Redis Cluster Re-Implemented in Rust: Scaling Redis Easily in Kubernetes
There is a parallel but less fancy reimplementation of Redis called Pedis:
https://github.com/fastio/1store
It's built using Seastar, which is sort of an ugh but cool unholy marriage of node.js and C++ ;-). It predates C++20 coroutines I guess, so you pass callbacks around like in Node. Maybe they have updated that by now.
They have also done a version of memcached using DPDK. I don't see a Pedis one, but check out their memcached one (scroll down): http://seastar.io/
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
What are some alternatives?
dragonfly - A modern replacement for Redis and Memcached
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
keydb-operator - A KeyDB (Drop-In Alternative to Redis) Operator for Kubernetes, based on Ansible Operator SDK.
undermoon-operator - Kubernetes Operator for Redis cluster based on Undermoon
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
undermoon - Mordern Redis Cluster solution for easy operation.
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
sky-benches - Attempts at benchmarking Skytable with the others to see where we stand
tikv - Distributed transactional key-value database, originally created to complement TiDB
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