valkey
KeyDB
valkey | KeyDB | |
---|---|---|
7 | 24 | |
13,508 | 10,780 | |
95.0% | 8.9% | |
9.5 | 8.4 | |
2 days ago | 24 days ago | |
C | C++ | |
GNU General Public License v3.0 or later | 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.
valkey
-
Valkey Is Rapidly Overtaking Redis
Changelog line items is probably a better measure (assuming the line items are aligned to features and bugfixes and not just a list of PRs) https://github.com/valkey-io/valkey/releases
Maybe version number/release cadence is also helpful.
-
Redis Is Forked
There were copious reference links in the article but the one that stood out to me and that I spent some time reading was this GitHub issues discussion on license [1] (but really on the differing opinions of two of the larger forks communities and values).
I am pleased that Valkey has made the decision to remain independent from the competing Redict fork project. The dogmatism on display in that thread is frustrating. It is one thing to stand by your own principles and opinions, it is entirely another thing to aggressively push your opinions onto others. With the two projects remaining independent, we will get to see which kind of community stewardship results in project success and longevity. The alternative, I fear, might have been technically minded people being railroaded by ideologically driven zealots.
Dogmatism and zealotry are words we probably mostly associate with religion, but I think they apply exactly to the kind of people I would proactively exclude from any public community I was trying to build.
1. https://github.com/valkey-io/valkey/issues/18#issuecomment-2...
-
New Redis Inc logo and branding [video]
At this time it's just better to focus on the Redis project that matters.
https://github.com/valkey-io/valkey
-
Redict 7.3.0, a copyleft fork of Redis, is now available
Time will tell if the version on Codeberg (https://codeberg.org/redict/redict) can compete with the fork on Github (https://github.com/valkey-io/valkey) in terms of visibility and contributions.
- Redis' license change and forking are a mess that everybody can feel bad about
- Valkey – a new project to resume development on the formerly open-source Redis
- ValKey is a new open-source Redis Fork
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?
monotone - embeddable cloud-native storage for events and time-series data
dragonfly - A modern replacement for Redis and Memcached
keydb-operator - A KeyDB (Drop-In Alternative to Redis) Operator for Kubernetes, based on Ansible Operator SDK.
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
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
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.
sled - the champagne of beta embedded databases
dynomite - A generic dynamo implementation for different k-v storage engines
Memcached - memcached development tree