OSS TanbouOn this page
Overview
Tokio is an event-driven, non-blocking I/O platform for asynchronous Rust applications. It combines a multithreaded task scheduler, an OS event-queue reactor, and asynchronous TCP/UDP sockets into a common runtime.
Features and best fit
Based on official documentation; not hands-on tested · Content checked:
Key features
Schedule asynchronous tasks around operating-system I/O events
Tokio provides a multithreaded work-stealing scheduler and a reactor backed by operating-system facilities such as epoll, kqueue, and IOCP. This lets I/O-heavy work progress without dedicating a thread to every waiting operation.
Sources: [2]
Use networking, timers, and tasks through one runtime
The README highlights asynchronous TCP and UDP sockets, while the crate exposes I/O, networking, scheduling, and timer facilities behind selectable Cargo features.
Sources: [2]
Best fit
Fits Rust backends handling many concurrent connections or I/O-bound tasks
It is a strong foundation for HTTP servers, proxies, streaming services, and other backends with substantial I/O concurrency, including stacks built with Axum, Hyper, Tonic, and related Tokio ecosystem crates.
Sources: [2]
Before adoption
Official sources
- [1]tokio-rs/tokio — GitHub repository(2026-10-06)
- [2]Tokio 1.53.2 — README(2026-10-06)
- [3]Tokio 1.53.2 release(2026-10-06)
Supplemental curator note
Tokio is the runtime foundation beneath frameworks and HTTP libraries such as Axum and Hyper rather than a web framework itself. For pinned minor versions, check both the LTS window and MSRV before standardizing on a release line.
Try it in 3 steps
- 1
Clone the reviewed Tokio release
Clone the reviewed Tokio 1.53.2 tag. A Rust toolchain with Cargo is required.
git clone --depth 1 --branch tokio-1.53.2 https://github.com/tokio-rs/tokio.git && cd tokio - 2
Start the TCP echo server
Run the official example, which listens on 127.0.0.1:8080. Keep this terminal running for the server.
cargo run --example echo-tcp - 3
Connect from another terminal
Run the official client example in another terminal, type a line, and confirm that the server echoes it back.
cargo run --example connect-tcp 127.0.0.1:8080
Growth
Growth trends · Last 30 days
33,338 Stars
Trend data is still being collected.
Built with
Categories and tags
GitHub data
GitHub dataView detailed GitHub data
GitHub Topics
- asynchronous
- networking
- rust
Related information
Write a related articleShare a guide or use case for this OSS in Markdown. Articles are published after administrator approval.
Explore next
- Diesel14,193 Stars
2 shared tag(s) · 1 shared category(s) · Same language
validate SQL queries and schemas with Rust's type system through an ORM and query builder
Rust - SeaORM9,914 Stars
2 shared tag(s) · 1 shared category(s) · Same language
manage asynchronous queries, relations, and migrations with a relational ORM for Rust
Rust - Loco9,397 Stars
2 shared tag(s) · 1 shared category(s) · Same language
bootstrap Rust backends with Rails-style conventions, generators, ORM, jobs, and storage
Rust - tracing6,909 Stars
2 shared tag(s) · 1 shared category(s) · Same language
record causal async execution with structured spans and events in Rust
Rust - Poem4,445 Stars
2 shared tag(s) · 1 shared category(s) · Same language
build Rust HTTP servers by composing routes, extractors, and middleware
Rust - Salvo4,438 Stars
2 shared tag(s) · 1 shared category(s) · Same language
build Rust web services with HTTP/1-3, OpenAPI, WebSockets, and integrated TLS features
Rust
Report incorrect information
Tell us if any listing information is incorrect or outdated.