mongo-rust-driver VS rust-embed

recently i came across this issue when trying to share a mongo client across tests, it turns out that a mongo client should only be used on the runtime that created it. is this something i should worry about for channels, or will they work if the sender & receiver are on different runtimes?

MongoDB Rust Driver

We start by simply getting all collections in a database. The MongoDB Rust driver provides a handy db.list_collection_names() that we can call to get all collections—and each collection is turned into a model for Prisma schema. 🥂

To see the full set of changes, check out the release notes . If you run into any issues, please file an issue on JIRA or on our GitHub repository.

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

you'd be better off asking in their repo. Also https://github.com/mongodb/mongo-rust-driver#requirements

As you're using MongoDB, it would be better to use warp instead because in their README they've stated:

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.