Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I just released a new major version of a redis client (fred) and I'd appreciate any feedback on it.
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.
When I first released this I did it on my personal github, and when I moved it to the azuqua github I did it on the condition that the entire thing be MIT licensed and that I would retain ownership over the crates.io release via my personal github.