Tendis
edis
Our great sponsors
| Tendis | edis | |
|---|---|---|
| 8 | 2 | |
| 2,822 | 466 | |
| 2.1% | - | |
| 8.2 | 0.0 | |
| 3 months ago | over 8 years ago | |
| C++ | Erlang | |
| GNU General Public License v3.0 or later | 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.
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.
- Tendis distributed storage engine, compatible with Redis protocol
- Tendis: A high-performance distributed storage system
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?
kvrocks - Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
KeyDB - A Multithreaded Fork of Redis
SSDB - SSDB - A fast NoSQL database, an alternative to Redis
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
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.
raids - Cache distribution services: http, websock, redis, memcached
Seastar - High performance server-side application framework
dynomite - A generic dynamo implementation for different k-v storage engines