Architectural Invariant Design: FastAPI ASGI Streaming Backpressure & Cooperative Task Cancellation Guardrail
FastAPI ASGI Streaming Backpressure & Cooperative Task Cancellation Guardrail defines an industrial-grade behavioral standard for backend engineering. Enforces strict cooperative cancellation and backpressure propagation between ASGI HTTP client disconnect events and underlying async generator pipelines. Prevents catastrophic worker thread starvation, uncollected generator frames, and phantom compute leaks by polling request disconnect status and handling asyncio.CancelledError during chunk yielding. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.
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 Mode | AI Symptom (The Anti-Pattern) | Severity | Production Impact & Remedy |
|---|---|---|---|
| AI Hallucination & Deprecation Drift | Silent Async Generator Execution Post-Client Disconnect Leading to Worker Thread Pool Starvation | 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 Inconsistency | AI 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. |
Step-by-Step Production Directives
Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:
Engineers MUST ALWAYS pass the raw `fastapi.Request` object into generator dependencies that feed `StreamingResponse` instances.
Engineers MUST ALWAYS pass the raw `fastapi.Request` object into generator dependencies that feed `StreamingResponse` instances.
Engineers MUST NOT yield tokens or chunks within an unmonitored `while` or `for` loop without actively probing `await request.is_disconnected()` or handling `asyncio.CancelledError`.
Engineers MUST NOT yield tokens or chunks within an unmonitored `while` or `for` loop without actively probing `await request.is_disconnected()` or handling `asyncio.CancelledError`.
Code SHOULD encapsulate streaming logic inside `try...finally` or asynchronous context managers to ensure immediate resource cleanup (e.g., closing database cursors, terminating LLM client connections, releasing locks) upon client abort.
Code SHOULD encapsulate streaming logic inside `try...finally` or asynchronous context managers to ensure immediate resource cleanup (e.g., closing database cursors, terminating LLM client connections, releasing locks) upon client abort.
Services MUST NEVER offload streaming generator iteration to unshielded background threads via `anyio.to_thread.run_sync` without an explicit cooperative cancellation token or timeout.
Services MUST NEVER offload streaming generator iteration to unshielded background threads via `anyio.to_thread.run_sync` without an explicit cooperative cancellation token or timeout.
Components NEVER swallow `asyncio.CancelledError` or catch generic `BaseException` without re-raising `asyncio.CancelledError` to allow the ASGI server event loop to tear down the task hierarchy cleanly.
Components NEVER swallow `asyncio.CancelledError` or catch generic `BaseException` without re-raising `asyncio.CancelledError` to allow the ASGI server event loop to tear down the task hierarchy cleanly.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is FastAPI ASGI Streaming Backpressure & Cooperative Task Cancellation Guardrail critical for AI coding assistants?
Enforces strict cooperative cancellation and backpressure propagation between ASGI HTTP client disconnect events and underlying async generator pipelines. Prevents catastrophic worker thread starvation, uncollected generator frames, and phantom compute leaks by polling request disconnect status and handling asyncio.CancelledError during chunk yielding. 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 (Silent Async Generator Execution Post-Client Disconnect Leading to Worker Thread Pool Starvation) 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.