mini-redis VS KeyDB

Hi, I'm trying to implement RESP with Rust (more like a mini-redis clone from tokio tutorial).

One project I found extremely easy to read and understand was mini-redis. Anything similar to that?

For learning async Rust, mini-redis repo is hard to surpass: https://github.com/tokio-rs/mini-redis

The code is simple enough for beginners to follow, but also complex enough to demonstrate Rust async in the wild. And best of all, the code is heavily commented!

You can follow the official Tokio tutorial to implement mini-redis incrementally: https://tokio.rs/tokio/tutorial/setup

for backend async service: https://github.com/tokio-rs/mini-redis

The official Tokio mini-Redis example has a well-documented example of shutting down worker tasks: https://github.com/tokio-rs/mini-redis/blob/master/src/shutdown.rs

Have a look at https://github.com/tokio-rs/mini-redis, written as an example of a modern rust application.

I sure learned a ton from looking at the mini-redis implementation from the tokio team https://github.com/tokio-rs/mini-redis -- especially when you want to work with tokio! I think it's remarkably well structured and documented.

If https://github.com/tokio-rs/mini-redis does not help answer your question, could you elaborate a bit more on your struggle and we can see if we can fit it into our docs.

Tokio async runtime for Rust has a tutorial in its user guide https://tokio.rs/tokio/tutorial on writing a mini-redis (https://github.com/tokio-rs/mini-redis).

You may be able to take inspiration from mini-redis, which is a learning resource created by the Tokio project. Its purpose is to show off many common patterns in async Rust, and a shared hashmap is one of them.

Three. KeyDB forked before the recent shake-up.

https://github.com/Snapchat/KeyDB

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...

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

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 posted about KeyDB, a multi-threaded fork of Redis, here already a while ago. We still use it in some cases and find it beneficial.