Five Years of Cloud Native Rust.
summary
Linkerd adopts Rust for the proxy data plane (chosen in 2018) and reports concrete wins: Linkerd data plane in Rust yields latencies near application baseline and far lower CPU and memory than Envoy, and Linkerd avoids the class of memory-corruption CVEs that cause ~90% of Android, ~60–70% of iOS/Mac, and ~70% of Chromium vulnerabilities. Development also funds ecosystem pieces—Tokio, hyper, tracing, kubars—while the control plane and CLI remain Go; a 2022 Rust policy controller ships and operates successfully.
AI-written summary · about
chapters (12)
- 0:00Introduction to talk
- 0:11What is Linkerd
- 1:14Why choose Rust
- 6:55Rust’s memory safety
- 9:21Code examples Rust vs C++
- 17:09Linkerd’s design principles
- 19:56Rust’s ecosystem in 2018
- 20:59Performance results
- 22:22Control plane in Go
- 23:05Writing Kubernetes controllers in Rust
- 24:10Why Rust matters today
- 25:10Q&A
related talks
31mWhy the future of the cloud will be built on Rust
13mLightning Talk: Writing Service Mesh Control Planes in Rust
44mPanel Discussion: Rust in the Cloud
05mRust Here, Rust There, Rust Everywhere! How a Crab Conquers the Cl...
04m"Scaling Safety: Rust at Google”
20mAn Empirical Study of Rust-for-Linux: The Success, Dissatisfaction, and Compromise
22mBuilding Cloud-native applications with Rust - the good, the bad and the ugly
56mWhen to Choose Rust