linkerd2-proxy VS tonic

Oh, there are many - https://lib.rs/crates/sfz is a simple one. If you're looking to proxy to something else, there's https://github.com/linkerd/linkerd2-proxy, etc.

Linkerd: Meant to be used in a kubernetes deploy, but the readme mentions possibilities of using it elsewhere.

I am really curious about Rust after looking for API proxies (in particular Linkerd2 - https://github.com/linkerd/linkerd2-proxy). Can anyone share her/his experience on going from Python to Rust? (bonus point if related to API :lol:)

Here is production ready service mesh using pre-1.0 crates: https://github.com/linkerd/linkerd2-proxy/blob/main/linkerd2-proxy/Cargo.toml

I know linkerd proxy is written in rust. You could look at that project to help get you started. Be aware that their use case is for very lightweight proxies inside of clusters so it might not fit your goals exactly.

Linkerd--a service mesh for Kubernetes--has featured a proxy written in Rust (since ~2017), but its control plane has been implemented entirely in Go... until now!

Its also heavily in linkerd-proxy https://github.com/linkerd/linkerd2-proxy which is a service mesh for kubernetes.

A build.rs file is used to generate Rust bindings at build-time.

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.