redka
SSDB
| redka | SSDB | |
|---|---|---|
| 3 | 14 | |
| 2,768 | 8,162 | |
| - | - | |
| 9.4 | 0.0 | |
| 3 days ago | almost 2 years ago | |
| Go | C++ | |
| BSD 3-clause "New" or "Revised" License | 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.
redka
-
Redis Re-Implemented with SQLite
I've decided to use the max connections approach for now.
[1]: https://github.com/nalgeon/redka/blob/main/internal/sqlx/db....
SSDB
-
Redis Re-Implemented with SQLite
I've used SSDB[0] in the past for some really stupid large datasets (20TB)_and it worked really well in production
[0] https://github.com/ideawu/ssdb
- The first version of Redis, written in Tcl
-
Building a distributed task queue in Python
> Or wanting to shift the architecture entirely to avoid using memory-bound Redis as a queue with an overflow risk.
I wanted to use SSDB[1] instead of Redis for that reason, but it doesn't support the necessary data structures.
[1] https://github.com/ideawu/ssdb
- I deleted 78% of my Redis container and it still works
-
How to store subscriptions? A practical guide and analysis of 3 selected databases A closer look into PostgreSQL, Redis, and DynamoDB.
There is also ssdb https://github.com/ideawu/ssdb
- SSDB
-
Tell HN: Memcached and Redis Considered Harmful
It's 2021 and we have extremely fast key-value lookups using LevelDB/RocksDB, but we're still using RAM-based caching tools [1] [2] [3]. It's time to consider RAM-based caching harmful, and start caching with SSDs for larger datasets and lower costs. For ex: SSDB [4]
[1] https://redis.io/
[2] https://memcached.org/
[3] https://news.ycombinator.com/item?id=29532552
[4] https://github.com/ideawu/ssdb#ssdb-vs-redis
- Drop-In Replacement for Memcached
-
Using a disk-based Redis clone to reduce AWS S3 bill
Aside from this particular use-case, which is what most people here are talking about -- I had never heard of the SSDB project, but it interests me because I often use Redis for certain things it's able to do, aside from its in-memory storage, and sometimes the fact that the data is not stored on disk is a bit of a drawback for me, something I have to work around.
- SSDB – A fast NoSQL database, an alternative to Redis
What are some alternatives?
rq - Simple job queues for Python
KeyDB - A Multithreaded Fork of Redis
redimo.go - Use the power of DynamoDB with the ease of the Redis API
kvrocks - Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
sqlite - Go SQLite3 driver
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
pocketbase - Open Source realtime backend in 1 file
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
sabledb - Ultra fast, persistent database supporting Redis API
Memcached - memcached development tree
dynomite - A generic dynamo implementation for different k-v storage engines
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.