How to switch from cozy NodeJS to scary Rust as a company.
summary
Company replaces a Node image microservice using sharp with a Rust implementation and measures big wins: 20% memory usage compared to Node, much faster startup and throughput, and small benchmarks showing 15x faster for trivial HTTP examples. Migration takes about a year, produces a rewritten office display app (Panic board rewrite), spawns CLI tools, and gets over 60% developers tried Rust so projects in production reduce CPU and hosting costs while being maintainable.
AI-written summary · about
chapters (13)
- 0:00Switching from NodeJS to Rust
- 2:52Faster backend alternative needed
- 5:01Rust syntax first impressions
- 8:10NodeJS vs Rust differences
- 11:25Rust not for everyone
- 13:51First Rust production project
- 16:40Performance gains from Rust
- 18:28Making Rust less intimidating
- 19:56Panic board rewrite with Rust
- 21:44Current Rust adoption
- 23:29Rust transition takeaways
- 24:56Why learn Rust
- 25:37Closing remarks
