Architecture
The Actor Model in Rust With Tokio Tasks and Channels
An actor is a task that owns its data and processes messages one at a time. Channels replace locks, and a handle type hides the plumbing.
4 min read
Tag
tokio
33 posts
Architecture
An In Process Event Bus in Rust With Broadcast Channels
An event bus lets parts of a program react to things without knowing about each other. Tokio's broadcast channel gives a small, typed one with built-in handling for slow subscribers.
4 min read
Testing
Testing Rate Limiters and Quotas in Rust Web Services
A limiter is a function of time, so tests should control time. Assert the boundaries: the last allowed request, the first rejected one and the moment capacity returns.
4 min read
ConcurrencyGuide
Build a Chat Server in Rust With Tokio Broadcast Channels
A chat room is a one to many fan out. Tokio's broadcast channel gives each client its own receiver, and lagging clients are handled for you.
17 min read
ConcurrencyGuide
Async Networking in Rust With Tokio TCP Listener and Stream
The core of every network service is an accept loop that spawns a task per connection. This walks through an echo server and a line protocol with Tokio, then adds limits.
22 min read
Concurrency
LocalSet and Non Send Futures in Tokio Explained Made Clear
tokio::spawn demands Send because tasks can move between threads. LocalSet pins tasks to one thread so Rc, RefCell and other !Send types can cross awaits.
7 min read
Concurrency
Tuning Tokio Worker Threads and When to Leave Defaults
The default of one worker per core is right for most services. Change it when a container limit misleads Tokio, or when measurements show queueing or contention.
6 min read
Concurrency
Tokio Metrics and Runtime Stats for Production Dashboards
The numbers that tell you a runtime is struggling are queue depth, worker busy time and poll counts. Tokio exposes them, and a small task exports them to Prometheus.
7 min read
ConcurrencyGuide
Debugging a Hung Async Rust Program Step by Step Explained
A hang is usually one of four things: a blocked runtime thread, a lock held across an await, a future that never wakes or a channel nobody closes. Here is the order to check them.
18 min read
Performance
Profiling Async Rust Services With Tokio Metrics in Steps
Use Tokio runtime and task metrics to see worker busy time, scheduling delay, queue depth and slow polls. Export them, read the numbers that matter and tell blocking code from a genuine lack of capacity.
3 min read
Testing
Testing Retry and Timeout Logic in Rust Without Sleeping
Retry and timeout code is full of delays, and sleeping in tests makes them slow and flaky. Use Tokio paused time, a scripted flaky dependency and an injected backoff to test every path in milliseconds.
4 min read
Testing
Testing Graceful Shutdown and Signal Handling in Rust Apps
Make shutdown testable by taking a shutdown future instead of listening for signals inside the server. Assert that in-flight requests finish, new ones are refused and the process exits within a deadline.
4 min read