kvrocks
SSDB
kvrocks | SSDB | |
---|---|---|
23 | 14 | |
3,460 | 8,175 | |
1.9% | - | |
9.6 | 0.0 | |
3 days ago | about 2 years ago | |
C++ | C++ | |
Apache License 2.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.
kvrocks
-
Redis Re-Implemented with SQLite
I switched from SSDB to Kvrocks recently, because SSDB is abandoned and the author missing for 3 years now. I used to recommend SSDB, but now there's better alternatives available:
https://github.com/apache/kvrocks
https://github.com/sabledb-io/sabledb
- Apache Kvrocks is a distributed key value NoSQL database that uses RocksDB as s
-
Five Apache projects you probably didn't know about
Another under the radar Apache project I've found myself using is Apache KvRocks
https://github.com/apache/kvrocks
It's a Redis compatible database on top of RocksDB, so unlike Redis it uses the disk instead of RAM, but you can control how much data is cached in RAM, obviously Kvrocks will be slower than Redis for uncached data.
Useful in situations where you want a KV data store that isn't limited by your memory specs but is compatible with everything that speaks Redis.
- Redis as a Database
- Apache Kvrocks: distributed store using RocksDB, Redis compatible protocol
-
Ask HN: Why are there no open source NVMe-native key value stores in 2023?
There’s Kvrocks. It uses the Redis protocol and it’s built on RocksDB https://github.com/apache/kvrocks
-
Getting started with Kvrocks and go-redis
Apache Kvrocks is a distributed key-value NoSQL database that uses RocksDB as a storage engine and is compatible with Redis protocol.
-
The first version of Redis, written in Tcl
We use Kvrocks[0] at work. It is Redis on disk, powered by "RocksDB" (hence the name) and compatible with most of the Redis clients since it respects the Redis protocol. It was incubated by Apache earlier this year.
It works great and the development is really active.
[0]: https://kvrocks.apache.org
- Kvrocks 2.0.6 is released
- Kvrocks 2.0.5 has integrated the RocksDB's blob 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?
Tendis - Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.
KeyDB - A Multithreaded Fork of Redis
pika - Pika is a Redis-Compatible database developed by Qihoo's infrastructure team.
pika - An open-source colour picker app for macOS
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
Memcached - memcached development tree
fastonosql_gui - FastoNoSQL is a crossplatform Redis, Memcached, SSDB, LevelDB, RocksDB, UnQLite, LMDB, ForestDB, Pika, Dynomite, KeyDB GUI management tool.
dynomite - A generic dynamo implementation for different k-v storage engines
solid_cache - A database-backed ActiveSupport::Cache::Store
memKeyDB - MemKeyDB is a fork of Redis, adjusted to store objects on both Intel Optane Persistent Memory and DRAM.