redis-protocol.rs
A Rust implementation of RESP2 and RESP3 (by aembke)
fred.rs
An async Redis client for Rust. (by aembke)
Our great sponsors
redis-protocol.rs | fred.rs | |
---|---|---|
2 | 3 | |
34 | 331 | |
- | - | |
3.9 | 6.5 | |
25 days ago | 6 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
redis-protocol.rs
Posts with mentions or reviews of redis-protocol.rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-24.
-
Redust: a new Redis client
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.
-
Fred v3.0.0
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.
fred.rs
Posts with mentions or reviews of fred.rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-18.
-
Meet Fred: The most awesome Redis client for Rust.
View on GitHub
-
Redust: a new Redis client
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.
-
Fred v3.0.0
I just released a new major version of a redis client (fred) and I'd appreciate any feedback on it.
What are some alternatives?
When comparing redis-protocol.rs and fred.rs you can also consider the following projects:
redismodule-rs - Rust API for Redis Modules API
redis-rs - Redis library for rust
crates.io - The Rust package registry
redust - A simple Redis client & RESP parser for Rust.