AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: rust-axum-tokio

Rust Axum & Tokio Production Concurrency Standard

Guardrails for Rust web services: manage Send + Sync bounds, avoid blocking Tokio worker threads, use bounded mpsc channels, and handle database connection pooling.

Prohibited Anti-Pattern: AI calls std::thread::sleep or std::fs in async Axum handlers, stalling the Tokio async runtime.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Rust Axum & Tokio Production Concurrency Standard - Guardrails for Rust web services: manage Send + Sync bounds, avoid blocking Tokio worker threads, use bounded mpsc channels, and handle database connection pooling.
globs: src/**/*.rs
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/rust-axum-tokio"
---

# Rust Axum & Tokio Production Concurrency Standard

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: AI calls std::thread::sleep or std::fs in async Axum handlers, stalling the Tokio async runtime.

## System Constraints
You are a principal Rust backend engineer building services with Axum and Tokio. Never block Tokio threads with synchronous operations; use tokio::task::spawn_blocking or tokio::fs. Axum handler state must be thread-safe (Arc<AppState>). Use thiserror for domain errors.

## Strict Guidelines
- Never use std::thread::sleep in async fn; use tokio::time::sleep.
- Offload heavy CPU-bound or blocking operations to tokio::task::spawn_blocking.
- Prefer bounded channels (tokio::sync::mpsc::channel(capacity)) to prevent unbounded memory growth under load.
- Implement IntoResponse for custom application Error enum using thiserror.

## Bad vs Good Implementations
### Non-blocking Axum Handler with Threadpool Offload

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: std::fs blocks the worker thread, starving other async tasks scheduled on that thread.
```rust
// Anti-pattern: Blocking synchronous file write in async handler
async fn upload_handler(body: Bytes) -> StatusCode {
    // CRITICAL: std::fs blocks the entire Tokio worker thread!
    std::fs::write("data.bin", body).unwrap();
    StatusCode::OK
}
```

#### Production Standard (Correct)
> **Standard**: Uses non-blocking tokio::fs and returns a typed AppError that maps cleanly into an HTTP response.
```rust
// Production Standard: Asynchronous Tokio I/O with error handling
use axum::{body::Bytes, http::StatusCode, response::IntoResponse};
use tokio::fs;

async fn upload_handler(body: Bytes) -> Result<StatusCode, AppError> {
    fs::write("data.bin", &body)
        .await
        .map_err(|e| AppError::Io(e.to_string()))?;
    Ok(StatusCode::OK)
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Cargo Clippy MCP
Run cargo clippy and audit lifetime and Send/Sync bounds.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Axum Error Handler Generator
Generate thiserror AppError and IntoResponse boilerplate for Axum.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Rust Axum & Tokio Production Concurrency Standard

Rust Axum & Tokio Production Concurrency Standard defines an industrial-grade behavioral standard for backend engineering. Guardrails for Rust web services: manage Send + Sync bounds, avoid blocking Tokio worker threads, use bounded mpsc channels, and handle database connection pooling. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI calls std::thread::sleep or std::fs in async Axum handlers, stalling the Tokio async runtime. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAI calls std::thread::sleep or std::fs in async Axum handlers, stalling the Tokio async runtime.Critical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Never use std

Never use std::thread::sleep in async fn; use tokio::time::sleep.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Offload heavy CPU-bound or blocking operations to tokio

Offload heavy CPU-bound or blocking operations to tokio::task::spawn_blocking.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Prefer bounded channels (tokio

Prefer bounded channels (tokio::sync::mpsc::channel(capacity)) to prevent unbounded memory growth under load.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Implement IntoResponse for custom application Error enum using thiserror.

Implement IntoResponse for custom application Error enum using thiserror.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Rust Axum & Tokio Production Concurrency Standard critical for AI coding assistants?

Guardrails for Rust web services: manage Send + Sync bounds, avoid blocking Tokio worker threads, use bounded mpsc channels, and handle database connection pooling. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI calls std::thread::sleep or std::fs in async Axum handlers, stalling the Tokio async runtime.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Rust