redis-rs VS rust-embed

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?

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.

We have been using it before it got merged in redis-rs (we upvoted the PR here https://github.com/mitsuhiko/redis-rs/pull/319 a while back ;-))

Ref: https://github.com/pyrossh/rust-embed/issues/205 Rust-embed behavior in debug mode is incompatible with cross-compilation. It nails a path from build time into the executable. Force release mode o"

Not sure how common it is exactly but I've definitely seen it done here and there and done it myself in some projects. Having self-contained binaries is super nice and avoids a fair few issues. rust-embed makes it even better.

They even accepted one of my feature requests to add some file metadata which makes doing this kind of thing easier: https://github.com/pyros2097/rust-embed/issues/140

Note: include_str! can make compilation a bit slow. The rust-embed crate can read files in debug mode as normal and embed the files in release mode.

For reference, there are examples for several frameworks in the rust-embed repo.

But then it turned out that the images can’t be read from the database due to the lack of GridFS support in MongoDB Rust Driver (open ticket). So for simplicity purposes, I decided to use rust_embed crate which allows including images in the application binary at compile time (at the development time they are loaded from a file system). (It is also possible to store images separately from the application; images folder should be mounted as a volume in the Docker Compose service definition)

Images of planets are included in the application binary at compile time using rust_embed crate (at the development time they are loaded from a file system).

Maybe rust-embed can help you? I haven't used it myself, just came across the crate on this sub a while ago.