redis-protocol.rs VS incubator-opendal

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.

I was reading through the code of databend: https://databend.rs/ It's a "wrapper" over datafusion and does a lot of similar things to Quickwit. And yeah, to drive the index cluster they rely on https://github.com/datafuselabs/openraft && https://github.com/datafuselabs/opendal. I'd be interested about you thoughts on the project if you've already heard about it too.

Announce OpenDAL for object storage data access