Drizzle ORM Prepared Statement Partitioning Boundary for Serverless Runtimes

--- description: Drizzle ORM Prepared Statement Partitioning Boundary for Serverless Runtimes - Enforces static isolation and memoized lifecycle boundaries for Drizzle ORM prepared queries across serverless microVMs and worker execution tiers. Prevents per-request re-preparation and unparameterized dynamic query emissions that cause database connection pool memory exhaustion, statement name collision, and query plan cache thrashing under high concurrency. globs: src/**/*.ts, src/**/*.dao.ts, src/**/*.repository.ts, lib/db/**/*.ts alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/drizzle-orm-prepared-statement-partitioning-boundary" --- # Drizzle ORM Prepared Statement Partitioning Boundary for Serverless Runtimes > **Severity**: CRITICAL | **Category**: backend > **Anti-Pattern Warning**: Compiling dynamic Drizzle prepared statements inside per-request execution scopes ## System Constraints You are a Principal Software Architect enforcing immutable prepared statement partitioning boundaries in Drizzle ORM. You must strictly forbid the instantiation or `.prepare()` invocation of SQL queries inside per-request handlers, serverless functions, or dynamic loops. Mandate module-scoped prepared statement declaration with deterministic statement naming and typed `sql.placeholder()` primitives to eliminate plan cache thrashing and per-request SQL AST compilation overhead. ## Strict Guidelines - Engineers MUST ALWAYS declare and compile prepared statements at the module level outside of per-request invocation handlers or event loops. - Engineers MUST NOT invoke `.prepare()` with dynamically generated or anonymized statement names inside request-scoped handlers. - Code MUST parameterize all variable dynamic inputs using `sql.placeholder('<param_name>')` instead of inline interpolated values or dynamic AST concatenations. - Services MUST assign globally unique, deterministic string identifiers to prepared queries when targeting stateful protocol adapters (e.g., node-postgres or pgBouncer in session mode). - Components NEVER execute raw ad-hoc queries for hot-path endpoints that can be modeled as parameterized, statically structured relational trees. ## Bad vs Good Implementations ### Module-Scoped Prepared Statements with Named Placeholders vs. Per-Request Compilation #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Calling `.prepare()` within a function handler recompiles the Drizzle query AST on every execution. In high-concurrency microVMs or pooled connections (e.g., pgBouncer), this rapidly leaks server-side prepared statements, floods the query cache, and increases event loop latency. ```typescript import { eq } from 'drizzle-orm'; import { db } from './db'; import { users } from './db/schema'; // ANTI-PATTERN: Query compiled and prepared inside the request path. // Causes plan cache thrashing, prepared statement memory leaks in Postgres/pgBouncer, // and redundant AST construction on every incoming request in microVMs. export async function handleGetUser(userId: string) { const statement = db .select() .from(users) .where(eq(users.id, userId)) .prepare(); // Generates unindexed anonymous statements or repeated names const result = await statement.execute(); return result[0] ?? null; } ``` #### Production Standard (Correct) > **Standard**: Declaring the prepared statement at the module boundary ensures that AST parsing, SQL generation, and driver-level parameter bindings occur strictly once per microVM lifecycle. The database can maintain a stable query plan across subsequent invocations. ```typescript import { eq, sql } from 'drizzle-orm'; import { db } from './db'; import { users } from './db/schema'; // PRODUCTION INVARIANT: Statically initialized and partitioned outside handler execution scope. // Prepared once per VM instance lifecycle with typed placeholders and an explicit unique statement identifier. export const selectUserByIdPrepared = db .select({ id: users.id, email: users.email, status: users.status, updatedAt: users.updatedAt, }) .from(users) .where(eq(users.id, sql.placeholder('userId'))) .prepare('query_users_by_id'); export async function handleGetUser(userId: string) { const [user] = await selectUserByIdPrepared.execute({ userId }); return user ?? null; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Drizzle ORM Prepared Statement Partitioning Boundary for Serverless Runtimes

Drizzle ORM Prepared Statement Partitioning Boundary for Serverless Runtimes defines an industrial-grade behavioral standard for backend engineering. Enforces static isolation and memoized lifecycle boundaries for Drizzle ORM prepared queries across serverless microVMs and worker execution tiers. Prevents per-request re-preparation and unparameterized dynamic query emissions that cause database connection pool memory exhaustion, statement name collision, and query plan cache thrashing under high concurrency. 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: Compiling dynamic Drizzle prepared statements inside per-request execution scopes 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Compiling dynamic Drizzle prepared statements inside per-request execution scopes	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.

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:

Engineers MUST ALWAYS declare and compile prepared statements at the module level outside of per-request invocation handlers or event loops.

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.