It performs better and uses different design choices (for example: SableDb uses tokio's local task per connection, and in general it uses green threads to make the code more readable and easy to maintain).
I will release some design documents later on (hopefully this month). Remember that is a one man project (hopefully, not for long), so it takes time to organize everything :)
Looks promising, but needs support for more than just strings and lists. I personally use hashes, sorted-sets, and sets more than lists in production apps, and probably others too?
Absolutely, adding more commands is my goal
Completing a full-sync replication is my first priority (I have currently implemented a WAL tailing from primary -> replica) but tailing from a snapshot is the ideal solution IMO here.
Once this in place, adding "hash" commands (hset, hget etc) is the next family of commands.
I open sourced it hopefully to get help from people out there :)
It would be informative to compare to memory only Redis and persistent Redis on the same hardware with the same benchmark suite. Even if SableDb is slower since it’s durably persisted, it would still be useful to consider the tradeoff versus ephemeral or weakly persisted implementation of the same API.
So it's a Redis API written in Rust, but the underlying database is all C++. It seems like a nice project, but perhaps a little misleading to say it's written in Rust.
hivacruz|1 year ago
https://github.com/apache/kvrocks/
SableDb|1 year ago
SableDb|1 year ago
I will release some design documents later on (hopefully this month). Remember that is a one man project (hopefully, not for long), so it takes time to organize everything :)
welder|1 year ago
https://github.com/sabledb-io/sabledb/issues/7
SableDb|1 year ago
Once this in place, adding "hash" commands (hset, hget etc) is the next family of commands. I open sourced it hopefully to get help from people out there :)
jitl|1 year ago
CyanLite2|1 year ago
https://microsoft.github.io/garnet/docs/benchmarking/results...
marcosdly|1 year ago
xedrac|1 year ago
vdfs|1 year ago
dboreham|1 year ago
pgwhalen|1 year ago
Or do you mean that LSMs shouldn’t be a foundation for a database?
rafaelturk|1 year ago