Tokio quiz

Test your Tokio knowledge with a free interactive quiz — 21 questions with answers and explanations. No signup needed to play.

What is a key difference between `tokio::spawn` and a native OS thread?

1. What is a key difference between `tokio::spawn` and a native OS thread?
2. What is a `Stream` in the context of Tokio/async Rust?
3. When many independent async tasks in a Tokio application need to share a piece of mutable state, what is the typical idiomatic approach?
4. What is `tokio::sync::oneshot` used for?
5. Why is Tokio a natural fit for building high-throughput web servers and network proxies in Rust?
6. What is `tokio::task::spawn_blocking` for?
7. What is `tokio::select!` used for?
8. Why would a network server built with Tokio typically outperform a naive thread-per-connection server under heavy load?
9. What is an `mpsc` channel in Tokio used for?
10. Why does Rust need a separate crate like Tokio for async, unlike languages such as JavaScript or Go?
11. What happens if a long-running, CPU-bound computation is run directly inside an `async fn` without special handling?
12. What does `tokio::sync::Mutex` offer that `std::sync::Mutex` does not, for use inside async code?

More quizzes