Tokio Patterns

This repository is a collection of Tokio (Rust async runtime) patterns and examples

Table of Contents

Part 1: $\color{yellow}{\textsf{Basic Operations}}$

Section 1. Manual Tokio Runtime Creation

Instead of using the #[tokio::main] macro, manually create a Tokio runtime

Section 2. Multithreaded Runtime

Configure the runtime to use 2 worker threads

Section 3. Current Thread Runtime vs Multithread Runtime

This code demonstrates how to create a single-threaded Tokio runtime using new_current_thread() instead of a multi-threaded runtime.

Part 2: $\color{yellow}{\textsf{Spawning}}$

Section 1: Async Function

This Rust code demonstrates basic asynchronous task spawning using the Tokio runtime.

Section 2: How Arc Shares Vector Data Across Multiple Tasks

This code demonstrates safe shared ownership of data across multiple asynchronous tasks using Arc

Section 3: Task Cancellation

This code demonstrates how to stop a running asynchronous task before it completes naturally.

Section 4: How Tokio Ensures Data is Send in Spawned Tasks

This code demonstrates Rust's Send trait enforcement for data shared across asynchronous tasks.

Part 3: $\color{yellow}{\textsf{Shared State}}$

Section 1. How Arc Shares Immutable Data Across Multiple Tasks

This code demonstrates reference-counted thread-safe sharing of immutable data using Arc

Section 2. How a Mutex Shares Mutable State

This code demonstrates safe concurrent access to shared mutable state using Arc and Mutex

Section 3. How RwLock Enables Multiple Concurrent Readers

This code demonstrates how RwLock (Read-Write Lock) enables multiple concurrent readers while maintaining exclusive access for writers.

Section 4. How Semaphores Limit Concurrent Access

A semaphore is a synchronization primitive that limits the number of tasks that can access a resource simultaneously.

Section 5. Deadlock Prevention in Concurrent Code

A deadlock occurs when two or more tasks are waiting for each other to release resources, creating a circular dependency where none can proceed.

Section 6. How Barriers Work for Task Synchronization

A Barrier is a synchronization point where tasks must wait until a specified number of tasks reach that point, then all proceed together.

Section 7. How Notify Works for Signaling Between Tasks

Notify is a simple, lightweight synchronization primitive for signaling between tasks. One task waits for a signal, another task sends it.

Section 8. How Watch Channels Broadcast State Changes

This code demonstrates how a watch channel broadcasts state changes to multiple receivers, where each receiver can observe the latest value.

Part 4: $\color{yellow}{\textsf{Channels}}$

Section 1. Tokio MPSC Channel Explanation

This document demonstrates asynchronous communication between tasks using Tokio's multi-producer, single-consumer (mpsc) channel.

Section 2. Tokio MPSC: Multiple Sender Tasks Explanation

This code demonstrates Tokio's multi-producer, single-consumer (mpsc) channel pattern, where multiple concurrent tasks send messages to a single receiver.

Section 3. Tokio MPSC Backpressure Handling

This code demonstrates how Tokio's mpsc (multi-producer, single-consumer) channel handles backpressure using a bounded buffer.

Section 4. Oneshot Channel: Request-Response Pattern

A oneshot channel is a specialized communication primitive in Tokio designed for single-use, one-time message passing between asynchronous tasks.

Section 5. Understanding Tokio Broadcast Channels

This code demonstrates how to use Tokio's broadcast channel to send messages from one sender to multiple receivers concurrently.

Section 6. How Tokio MPSC Channels Handle Sender Drops and Closure

When working with Tokio's mpsc channels, understanding how channel closure works is crucial for building reliable concurrent applications

Section 7. Understanding try_send in Tokio MPSC Channels

Tokio's mpsc channels provide two main methods for sending messages: send() and try_send().

Section 8. Request-Response Pattern in Tokio Using Oneshot Channels

The request-response pattern is a common communication pattern where a client sends a request to a worker and waits for a response.

Section 9. Using tokio::select! to Wait on Multiple Channels

The tokio::select! macro allows you to wait on multiple async operations simultaneously and proceed with whichever completes first.

Part 5: $\color{yellow}{\textsf{I/O}}$

Section 1. Asynchronous File Reading in Rust with Tokio

This code explains how to write files asynchronously with Tokio.

Section 2. Asynchronous File Writing in Rust with Tokio

This code explains how to read files asynchronously with Tokio.

Section 3. Async File Copy in Rust with Tokio

This code explains how to read copy asynchronously with Tokio.

Section 4. Reading a File Line by Line with Tokio's BufReader

This code explains how to use Tokio's BufReader to read files asynchronously.

Section 5. TCP Echo Server in Rust with Tokio

This code implements a simple asynchronous TCP echo server using Rust and the Tokio runtime.

Section 6. TCP Client in Rust with Tokio

This code creates a TCP (Transmission Control Protocol) client that connects to a server, sends data, and receives a response.

Section 7. TCP Stream Splitting in Tokio

This document explains how Tokio allows you to split a TCP stream into separate read and write halves, enabling concurrent read and write operations on the same connection.

Section 8. TCP Stream Splitting in Tokio

This document explains how Tokio allows you to split a TCP stream into separate read and write halves, enabling concurrent read and write operations on the same connection.

Section 9. Understanding Tokio Timeout with I/O Operations

This document explains how to add timeouts to asynchronous I/O operations in Rust using tokio::time::timeout.

Part 6: $\color{yellow}{\textsf{Framing}}$

Section 1. Understandi1ng LinesCodec in Tokio

LinesCodec is a decoder/encoder that handles newline-delimited text protocols.

Section 2. Framed TCP Messaging with SinkExt

This code demonstrates how to use SinkExt from the futures crate to send framed messages over a TCP stream in Rust.

Section 3. Length-Delimited Framing in Rust with LengthDelimitedCodec

The LengthDelimitedCodec from the tokio-util crate provides automatic message framing for TCP streams by prefixing each message with its length.

Section 4. Custom Decoder Implementation for a Simple Protocol

This document explains how to implement a custom decoder using Tokio's Decoder trait for a simple binary protocol.

Section 5. Custom Encoder Implementation for a Simple Protocol

This code implements a custom encoder for a simple binary protocol using Tokio's Encoder trait.

Section 6. Complete Codec Implementation: Encoder and Decoder

This code demonstrates how to create a unified codec struct that implements both the Encoder and Decoder traits from Tokio for bidirectional communication over network connections.

Section 7. JSON Codec with Length Prefixes

This code creates a custom codec that combines JSON serialization with length-delimited framing.

Section 8. Handling Partial Frames in a Custom Decoder

This decoder implements a length-prefixed protocol that gracefully handles partial frames - situations where a complete message hasn't arrived yet over the network.

Part 7: $\color{yellow}{\textsf{Async in Depth}}$

Section 1. Future Trait Basics

When you declare a function with async fn, Rust automatically transforms it into a function that returns a type implementing Future.

Section 2. Returning Different Future Types Using Trait Objects in Rust

Each async fn creates a unique, anonymous future type. Even though both functions have the same signature, they generate different types:

Section 3. Manual Future Implementation

The Future trait is the foundation of async/await in Rust:

Section 4. Creating a Future That Returns Pending Once Before Completing

This code demonstrates a fundamental async pattern: returning Pending to defer completion.

Section 5. Understanding Pinning in Self-Referential Structs

This code explains how pinning works in a self-referential struct.

Section 6. Understanding Async Blocks and Lazy Execution in Rust

An async block is a way to create a future inline.

Section 7. Running Multiple Futures Concurrently with tokio::join!

tokio::join! is a macro that runs multiple futures concurrently and waits for all of them to complete:

Section 8. Handling Multiple Fallible Futures with tokio::try_join!

tokio::try_join! is a variant of tokio::join! designed specifically for futures that return Result.

Section 9. Building a Simple Future Executor with Custom Waker

An executor is the runtime system that drives futures to completion.

Part 8: $\color{yellow}{\textsf{Select}}$

Section 1. Understanding tokio::select! - Waiting for the First Operation

The select! macro polls multiple async operations concurrently and proceeds with whichever one completes first.

Section 2. Understanding tokio::select! - Channel Receive with Timeout

This code demonstrates a common async pattern: attempting to receive a message from a channel with a timeout.

Section 3. Pattern Matching with Enum Messages in Tokio Channels

This code demonstrates how to use Rust's pattern matching to handle different types of messages received from a tokio channel.

Section 4. Using tokio::select! in a Loop with Multiple Channels

This code demonstrates a common async pattern: attempting to receive a message from a channel with a timeout.

Section 5. Understanding Biased Selection in tokio::select!

This code demonstrates how to use biased selection in tokio::select! to prioritize certain branches over others. By default, select!

Section 6. Handling Cancellation-Unsafe Operations in tokio::select!

This code demonstrates how to correctly handle cancellation-unsafe operations when using tokio::select!.

Section 7.

This code demonstrates how to use tokio::select! to concurrently wait on three different types of Tokio channels: MPSC, Oneshot, and Broadcast.

Section 8. Graceful Shutdown Pattern with tokio::select!

This code demonstrates a graceful shutdown pattern - one of the most important patterns in async Rust programming.

Section 9. Resetting Timeout Pattern with tokio::select!

This code demonstrates a resetting timeout pattern - a technique where a timeout is continuously reset each time activity occurs.

Part 9: $\color{yellow}{\textsf{Streams}}$

Section 1. Iterating Over Streams with while let Some

This code demonstrates how to iterate over an async stream using the while let Some pattern.

Section 2. Creating Streams from Iterators with tokio

This code demonstrates how to convert a synchronous iterator (like a Vec) into an asynchronous Stream using tokio_stream::iter.

Section 3. Transforming Stream Values with the map Combinator

This code demonstrates how to use the map combinator to transform values in a stream.

Section 4. Transforming Stream Values with the filter Combinator

This code demonstrates how to use the filter combinator to selectively keep values in a stream based on a condition.

Section 5. Async Stream Transformations with the then Combinator

This code demonstrates how to use the then combinator to perform asynchronous transformations on stream values.

Section 6.

Section 7.

Section 8.

Section 9.