transmitic VS linkerd2-proxy

I use it for a desktop file transfer app [0]. I chose Rust because my primary language is Python and I just wanted to learn something new and really different for this project. Go would have been easier, but Rust just feels bullet proof. It's so strict. If it compiles, it works! It's been a very interesting journey.

[0] https://github.com/transmitic/transmitic

I've built a p2p file transfer program [0]. All my development experience had been in Python, but I really wanted to try a statically typed, low level language, and decided to give rust a try.

It was hard to get going, and I still only know basics, but everything just works! Typing, borrow checker, the matched results, all of that makes code bullet proof.

[0] https://github.com/transmitic/transmitic

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.