redis-protocol.rs VS redis-rs

For what it's worth - here's a library I use in my redis client for parsing RESP2 and RESP3. It does not use serde but does use nom, and it has an optional feature that can decode `BytesMut` without moving or copying the buffer contents as long as you're willing to use the `Bytes` ecosystem types.

The latest version is a complete rewrite on async/await, tokio 1.x, the latest redis-protocol, etc. It has fundamentally different design goals compared to the popular redis-rs library and is more opinionated in its dependencies, specifically regarding tokio vs async-std, so it's probably not the right choice for certain use cases as a result. Redis-rs works well, but when we originally adopted Rust at Azuqua we had different design concerns for our Redis client and this library naturally grew in a different direction as a result.

The goto Redis client for Rust is called redis-rs. It has over 3k stars on Github. but I found it very annoying to use because I quickly found out that if you want to set any value you had to get a mutable reference to the underlying client. Which meant great pain to store Redis client in the global scope. People who do not know what a mutable reference is consider the let keyword in JavaScript. you can mutate or change a variable that is initiated with let.

staticpi, is a websocket forwarding service. Basically, it enables one to keep a Raspberry pi, or any computer, “connected”, in order to send and receive messages to and from any client, without having to deal with a static IP address, open ports on your router, or similar. Built in Rust, using axum, which in turn uses tungestine-rs for the websocket connections, tokio, sqlx, redis-rs and others.

redis (use streams and pubsub)

Are you addressing the long-standing issue that the redis client has related to dropped connections?

redis: by far the most popular and definitely the most ergonomic library. However, I was frustrated by its pubsub support; while generally acceptable, it's impossible to perform subscription operations while consuming messages. I like the library, but the workarounds to this issue were unacceptable to me.

I switched to LALRPOP for gluon but I still use combine in https://github.com/mitsuhiko/redis-rs and some other projects which need to parse "protocols" (less need for good error messages/error recovery and more need for speed).

The project is implemented with MongoDB Rust driver and redis-rs crate.

redis-rs, a Rust library for Redis with both high and low-level APIs

I think the redis crate was a well-organized API library. It's still sometimes hard to know the right things to make public and I think they nailed it.