Beyond Go and Python
For years, operations tooling has evolved in a predictable arc: Bash scripts for glue, Python for automation, and then Go as the language of cloud-native infrastructure. Kubernetes, Docker, Terraform, and most of the CNCF ecosystem are written in Go. So why introduce yet another language into an already complex stack?
Think of it this way: Go is like a modern, well-equipped workshop — safe, organized, and fast enough for almost any job. Rust is like a precision machinist's lathe — harder to operate, but capable of tolerances that no other tool can achieve. You don't replace the workshop with the lathe; you add the lathe when the job demands it.
Rust is a systems programming language, meaning it operates at the same low level as C and C++. It gives you fine-grained control over exactly how memory is allocated, laid out, and freed. The game-changer is that Rust provides this power without the memory bugs that plague C/C++ (buffer overflows, use-after-free, null pointer dereferences), and without the overhead of a Garbage Collector (GC) like Go or Java use. For infrastructure components that must be highly performant, absolutely reliable, and secure — like service mesh proxies, low-level node agents, or high-throughput data planes — Rust is rapidly becoming the tool of choice.
Real-world evidence: Linkerd2-proxy (the data plane of the Linkerd service mesh) is written in Rust. AWS Firecracker (the microVM technology powering Lambda and Fargate) is written in Rust. Cloudflare's Pingora (their replacement for NGINX, handling over a trillion requests per day) is written in Rust. These are not toy projects — they are production infrastructure at planetary scale.
Interviewers at companies using Rust in infrastructure (AWS, Cloudflare, Datadog, Microsoft) often ask: "Why would you choose Rust over Go for a systems component?" The defensible answer is: "When you need deterministic latency (no GC pauses), minimal memory footprint, or compile-time data-race freedom — and you can afford the longer development cycle. Go is the right default; Rust is the right choice when Go's trade-offs become bottlenecks."