Seven Rust Crates That Replace Homegrown Infrastructure
These crates let a small Rust team replace what used to be separate services: a search engine, a data processing pipeline, and a plugin sandbox, all inside a single binary. That changes the cost of shipping tools with real product capabilities.
Seven Rust crates now handle the jobs that used to force teams into assembling separate services or hand-written utilities. Tokio schedules async tasks and I/O events; Serde separates data models from serialization formats; Ratatui gives terminal tools a frame-based rendering model; GPUI provides a GPU-accelerated native UI framework from the Zed editor; Polars embeds a columnar query engine with lazy execution; Tantivy brings Lucene-style full-text search in-process; Wasmtime runs WebAssembly plugins under explicit capability grants.
The crates fall into three tiers. Tokio and Serde are base libraries that change how most code is written. Ratatui and GPUI are frameworks that shape application structure. Polars, Tantivy, and Wasmtime are embeddable engines that add a major capability while leaving operational responsibility with you. The author's test for adoption: use a crate only when it replaces something you would otherwise have to design, test, and run yourself. GPUI is the outlier; it's not yet 1.0, tied to Zed's roadmap, and needs evaluation for accessibility, OS coverage, and ecosystem maturity before a team bets on it.
The distinction between "useful" and "should use" is a practical heuristic for keeping dependency trees purposeful, especially in a language where pulling a crate is cheap.
The maturity gap between GPUI and the other six crates shows that a promising framework can still be a risky pick when the ecosystem around it hasn't settled.
The article treats each crate as replacing a specific hand-rolled system, suggesting that the Rust ecosystem's value is moving from primitives to complete engineering solutions.