Zen and the Art of Convincing Your Company to Use Rust
summary
NPM runs Rust in production since late 2016 and uses it for store file transforms and tiny microservices behind a change-follower architecture built with Tokio async code. Tooling includes Cargo/crates.io, rustup, rustdoc, rustfmt and Clippy. A naïve Rust log parser is initially slower than Node until buffer sizing and release builds are applied — real-world tuning yields ~3× faster or orders of magnitude gains (525 → 50,000 r/s) and a $4,000/month AWS bill drops into the free tier. The transform service ships for two years with zero alerts.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:12How many people write Rust
- 5:03What is Rust
- 8:35Dont rewrite your software
- 12:42How the NPM registry works
- 14:38Dont sell rust
- 16:16Not everyone will love everything
- 18:30Sell Sell Sell
- 25:41Programming
- 26:26Be Prepared
- 29:54Learning Curve
- 32:53Making Risk Correct
- 37:53Dont Change Everything at Once
related talks
38mHow I Convinced the World's Largest Package Manager to Use Rust, and So Can You!
27mHow to switch from cozy NodeJS to scary Rust as a company.
25mWTF, Rust for Web Development??
44mPanel Discussion: Rust in the Cloud
59mRust in Production
21mRust - Cargo Cult?
27mThe State of Rust Web Frameworks: Pros, Cons & Use Cases
33mRust at Sentry: 7 Years Later