3 ms·
For those that care, the core of linkerd 2.0 is in Rust https://github.com/linkerd/linkerd2-proxy https://github.com/linkerd/linkerd2-proxy
by sitkack 8y ago
For those that care, the core of linkerd 2.0 is in Rust
https://github.com/linkerd/linkerd2-proxy https://github.com/linkerd/linkerd2-proxy
- carllerche 8y agoAlso, a lot of the work on Tokio [1], Tower [2], and the Rust HTTP/2.0 implementation [3] is being driven by linkerd 2.0 (and sponsored by Buoyant). [1]: http://github.com/tokio-rs/tokio http://github.com/tokio-rs/tokio [2]: http://github.com/tower-rs/tower http://github.com/tower-rs/tower [3]: https://github.com/carllerche/h2 https://github.com/carllerche/h2
- otterley 8y agoDo you know why they migrated from Scala?
- jazoom 8y agoA JVM attached as a sidecar to each pod is a waste of resources. Garbage collection isn't great for a high performance proxy.
- deleted 8y ago[deleted]
- williamallthing 8y agoExactly! We considered Go briefly but in the end, the magic intersection of native-code performance, plus guaranteed memory safety, trumped every other concern for the data plane.
- otterley 8y agoIs there a significant demonstrable performance difference between Linkerd 2 and Envoy as a result?
- Thaxll 8y agoWhy do you call that core, only the sidecar is written in Rust all the rest is Go I think.