Tendis
KeyDB
Our great sponsors
Tendis | KeyDB | |
---|---|---|
8 | 23 | |
2,796 | 9,823 | |
1.8% | 12.6% | |
8.2 | 8.6 | |
2 months ago | 2 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.
Tendis
- Redis as a Database
- I deleted 78% of my Redis container and it still works
- Redis Cluster Re-Implemented in Rust: Scaling Redis Easily in Kubernetes
- IceFireDB: Distributed disk storage database based on Raft and Redis protocol
-
IceFireDB:Distributed disk storage database based on Raft and Redis protocol.
There is a project called Tendis, the architecture of IceFireDB is different from it, but they are all based on disk storage and resp protocol. Thank you for your attention and contact at any time
-
KeyDB CEO Interview: Getting into YC with a Fork of Redis
Does anyone have any experience with these other Redis clones? I need to write a benchmark on these someday (the outline for the blog post is already written), but have restricted my yak shaving recently:
- https://github.com/Tencent/Tendis
- https://github.com/Netflix/dynomite
On a separate note, is FLASH supposed to be an acronym? I can't tell if they're referring to flash storage (SSD, NVMe) or they're referring to perhaps a special algorithm that uses flash storage +/- some other features, or some altogether proprietary hardware.
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
-
Redis License Changed
Check out DragonflyDB (BSL): https://www.dragonflydb.io/
BSL is not OSI-approved, but it’s a much more reasonable AWS-resistant license. It’s the same license CockroachDB uses, for example.
KeyDB (BSL, acquired by Snapchat) is also an option: https://keydb.dev/
BSL is a much better license, but it’s a gamble on how long KeyDB will be supported. I don’t want to mess around with such a core part of my architecture.
-
The first version of Redis, written in Tcl
I think this is relevant... These are 3 OSS databases that can be an alternative to Redis:
- KeyDB: https://github.com/snapchat/keydb
- Dragonfly: https://github.com/dragonflydb/dragonfly
- Skytable: https://github.com/skytable/skytable
I have used keyDB before. The raft consensus makes building an HA Redis easy.
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).
- I deleted 78% of my Redis container and it still works
-
So, you call yourself the fastest key/value store? It's 5X, 10x and 25X faster
- KeyDB: https://github.com/snapchat/keydb
-
Global Presence; I made a thing
KeyDB is a fork of (everyone's favourite cache store) Redis, and it's messaging protocol and API is 100% compatible with Redis. What that means is you can just point any Redis client (like Hiredis or redis-rb) at a KeyDB instance, and it'll Just Work™️, with no changes required. The KeyDB selling points are: 1) multi-threading by default, and a lot of work was ploughed in to high performance around multi-threading in KeyDB, 2) compatible with all the features of regular Redis, 3) some advanced features which Redis only offers in it's paid/enterprise version are included for free in KeyDB, and the big one for me is multi-active replication, which is what I'm playing with here.
What are some alternatives?
dragonfly - A modern replacement for Redis and Memcached
keydb-operator - A KeyDB (Drop-In Alternative to Redis) Operator for Kubernetes
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
kvrocks - Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
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
IceFireDB - @IceFireLabs -> IceFireDB is a database built for web3.0 It strives to fill the gap between web2 and web3.0 with a friendly database experience, making web3 application data storage more convenient, and making it easier for web2 applications to achieve decentralization and data immutability.
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