rust-embed VS tonic

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.

Use tonic-build directly from Rust.

} // Omit the remaining code and refer to the example in Tonic: https://github.com/hyperium/tonic/blob/master/examples/src/multiplex/server.rs ```

If I’m not misunderstanding, you could both decode the gRPC protobuf AND write to delta lake in Rust. Tonic, Delta-rs.

Original post: https://github.com/hyperium/tonic/issues/1405. Cross-post here in case the problem is not specific to tonic.

Tonic

Just to double check Is this the correct repo?

Wasm isn't involved much actually. Basically, the frontend asks the backend to perform a gRPC call on its behalf using Tauri events. They are like named channels on which you can send any serde-compatible value. But the backend is a normal Rust program so there are no constraints there. I use prost-reflect to encode/decode Protobuf messages according to Protobuf descriptors loaded at runtime and make the actual requests using tonic from the tokio ecosystem. prost-reflect is necessary because, normally, tonic expects the Protobuf descriptor to be known at compile time so it can make some code generation behind the scenes.

You could have a look at gRPC i.e. https://github.com/hyperium/tonic

Looking at this example code: https://github.com/hyperium/tonic/blob/master/examples/src/tower/server.rs

The remaining gap is remote actors, since you still need some kind of serialization between them, and take your pick of standards for that one such as gRPC using Tonic.