Why I Needed Rust: Finally, Infrastructure Automation I can sleep on
summary
Claims that modeling infrastructure as types and using the compiler to pre-validate configs cuts wakeups and MTTR from about 30 minutes to ~5 minutes and makes automation deterministic. A provisioning system is built in Rust that validates semantics with Nickel, runs orchestration via Nushell, and deserializes shaped config with Serde; it encodes constraints as enums/traits, uses a DAG for dependencies, is deployed in production (including blockchain and backup cases), and it works.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:31Infrastructure automation eras
- 5:22Restaurant problem in infra
- 10:19YAML and JSON limits
- 13:10Unanswered automation questions
- 15:21Rust changes paradigm
- 18:54Human impact on automation
- 20:39Nickel and Nushell in Rust
- 23:50Dependency graphs and type safety
- 26:37Recovery time with Rust
- 27:19Why Rust matters
related talks
22mUsing Rust in Metal Fabrication
32mBuilding and Maintaining Rust at Scale
17mRust in Production
40mWhy Rust?
56mRust for Safe and Scalable Automotive: Insights from
22mRust as a Foundation for a Safe and Sustainable Future
11mLightning Talk: The Humble Rustacean: Human Factors Behind Rust’s Success
27mHow to (not) introduce Rust at your workplace - a tale