Panel Discussion: Rust in the Cloud
summary
Cloud-native Rust discussion lists concrete wins and tools: linkerd built on a Rust proxy and AWS Firecracker are production examples, Tokio is the async runtime driving network services, and projects like Parsec and mini-redis show real repos to join. Claims include fewer PagerDuty wakeups for Rust services and anecdotal infra cost reductions (one rewrite reports ~10x). Expect faster startup, wasm support, richer tooling, and steady ecosystem maturity over the next few years.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:05Rust in the Cloud Panel discussion
- 3:02"Rust in the Cloud". What have you been working on in this area, and what have you learned?
- 15:09Is there something about Rust makes it a particularly good fit for the cloud?
- 30:25What's the best way for the audience to get involved in cloud-related Rust efforts?
related talks
54mHelp, my whole team started coding in Rust
54mRust, Kubernetes, and the Cloud
25mWTF, Rust for Web Development??
38mPanel: Rust in reality
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
46mZen and the Art of Convincing Your Company to Use Rust
26mJavaScript Won the Web, Rust Is Taking the Critical Path
56mWhen to Choose Rust
