Architectural Invariant Design: FastAPI Async Generator SSE Lifespan and Disconnection Invariant
FastAPI Async Generator SSE Lifespan and Disconnection Invariant defines an industrial-grade behavioral standard for backend engineering. Enforces proactive ASGI client disconnection polling and rigorous task cancellation cleanup in FastAPI Server-Sent Events (SSE) generators. Eliminates silent async connection pool exhaustion caused by orphaned generator tasks continuing to stream after abrupt client termination. 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 | Zombie Async Generators Silently Draining Connection Pools Post-Client Disconnect | 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 inject the ASGI `Request` dependency into streaming endpoints and explicitly poll `await request.is_disconnected()` on every generator iteration.
Engineers MUST ALWAYS inject the ASGI `Request` dependency into streaming endpoints and explicitly poll `await request.is_disconnected()` on every generator iteration.
Engineers MUST wrap all async generator lifecycles in `try...finally` blocks to guarantee immediate closure of database sessions, Redis pub/sub consumers, or message brokers when a stream terminates.
Engineers MUST wrap all async generator lifecycles in `try...finally` blocks to guarantee immediate closure of database sessions, Redis pub/sub consumers, or message brokers when a stream terminates.
Engineers MUST NOT inject long-lived, per-request transactional dependencies (such as active `AsyncSession` instances) directly into the route parameters of infinite streaming generators.
Engineers MUST NOT inject long-lived, per-request transactional dependencies (such as active `AsyncSession` instances) directly into the route parameters of infinite streaming generators.
Code SHOULD explicitly handle `asyncio.CancelledError` within stream tasks, re-raising it only after releasing leased resources back to their respective connection pools.
Code SHOULD explicitly handle `asyncio.CancelledError` within stream tasks, re-raising it only after releasing leased resources back to their respective connection pools.
Services MUST emit standard SSE headers (`Cache-Control
Services MUST emit standard SSE headers (`Cache-Control: no-cache`, `Connection: keep-alive`, `X-Accel-Buffering: no`) to prevent intermediate proxy buffering from masking client disconnections.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is FastAPI Async Generator SSE Lifespan and Disconnection Invariant critical for AI coding assistants?
Enforces proactive ASGI client disconnection polling and rigorous task cancellation cleanup in FastAPI Server-Sent Events (SSE) generators. Eliminates silent async connection pool exhaustion caused by orphaned generator tasks continuing to stream after abrupt client termination. 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 (Zombie Async Generators Silently Draining Connection Pools Post-Client Disconnect) 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.