Tokio
Building async Rust services, Writing reliable asynchronous applications
It's the dominant but complex async runtime for Rust, where misuse can cause major performance issues without clear errors.
When blocking on worker threads (tanks throughput), Using tokio::spawn with local variables (lifetime complaints)
Related Tools
FIRST-HAND READS
What people reported, in their own words. Every line links to where it was said.
“great primatives in Rust like rustls (modern openSSL) and Tokio (async)”
POSITIVE · features · Hacker News · 2026-06-09
“Tokio + Axum, etc. I have seen very few issues with either of the above”
POSITIVE · performance · Hacker News · 2026-05-26
“Building that correctly on top of hyper/tokio myself would have been the bulk of the project, and I'd have shipped a worse version of what Sōzu already does.”
NEGATIVE · features · Hacker News · 2026-05-19
“Tokio and Axum make it quite friendly, and depending on what you are connecting to it becomes super easy, barely and inconvenience”
POSITIVE · ease of use · Hacker News · 2026-05-13
“I thought it was pretty cool you could opt into tokio for the bulk of async request work”
POSITIVE · features · Hacker News · 2026-05-05
“I highly recommend turning on when working with tokio: clippy::future_not_send. Forces all your futures to be Send, unless you opt out, which really helps keep the reasoning local”
MIXED · ease of use · Hacker News · 2026-05-03
“Blocking on Tokio worker threads can quietly tank throughput and explode p99 latency, all without panics or anything obvious in the logs”
NEGATIVE · performance · Hacker News · 2026-01-30
Have You Used This Tool?
Sign in to share your experience with this tool.
Sign in