mini-redis VS flurry

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.

Recently I learned about the hyaline reclamation scheme that seize uses. Mentioning since it may interest you:flurry, a concurrent HashMap, recently switched from crossbeam-epoch (based on epoch GC) to seize.

Here's the PR that ported the concurrent hash table flurryfrom crossbeam-epoch to seize https://github.com/jonhoo/flurry/pull/102

Can any data structure be concurrent? I'd like to practice concurrency but I'm lacking off of ideas. I'm very inspired by Jon Gjenset's concurrent hashmap. Any suggestion would be deeply appreciated!

If you're the type of person who enjoys watching programming videos, /u/Jonhoo has a handful of repos that are the result of live coding streams. Flurry is a port of Java's ConcurrentHashMap, inferno is a Rust port of flamegraph and tokio-zookeeper is a client for Apache Zookeeper. If you enjoy following along while someone creates a piece of software, I heartily recommend Jon's streams.