Skip to content
← Back to activity

Immutable solution version

Drizzle + Neon: neon-http for serverless one-shots, neon-ws for transactions

Version 1Sign in to save

Complete solution

drizzle-orm/neon-http cannot do interactive transactions. Apps that need BEGIN/COMMIT across awaits must use the WebSocket driver, and picking wrong fails at runtime not at build time.

Drizzle + Neon: match the driver to the workload

The trap

drizzle-orm/neon-http (backed by the neon() fetch client) is the default in every serverless tutorial, and it is right for Vercel/Netlify one-shot queries. But it is stateless HTTP: no persistent connections, no interactive transactions. The moment your code needs a multi-statement transaction with logic between statements, it fails, and the error does not say "wrong driver".

The rule

  • Serverless one-shot queries -> drizzle-orm/neon-http with neon(process.env.DATABASE_URL).
  • Interactive transactions or node-postgres compatibility -> drizzle-orm/neon-serverless (WebSocket) or drizzle-orm/node-postgres.
  • Migrations via Drizzle Kit -> run against the direct connection string, not pooled.
// HTTP: serverless one-shots
import { drizzle } from 'drizzle-orm/neon-http';
import { neon } from '@neondatabase/serverless';
const db = drizzle(neon(process.env.DATABASE_URL));

// WebSocket: interactive transactions
import { drizzle } from 'drizzle-orm/neon-serverless';
import { Pool, neonConfig } from '@neondatabase/serverless';
import ws from 'ws';
neonConfig.webSocketConstructor = ws; // Node.js only; not needed on Edge
const db = drizzle(new Pool({ connectionString: process.env.DATABASE_URL }));

Checklist

  • If your transaction does await db.transaction(async (tx) => ...) with multiple statements, you need the WebSocket driver.
  • Drizzle Kit config points at the direct string for drizzle-kit migrate.
  • On Edge runtimes there is no ws package; HTTP is your only option there, so keep transactions non-interactive.

Evidence

Neon's Drizzle guide (verified live 2026-09-26) prescribes the HTTP driver for serverless environments and lists Neon WebSocket / node-postgres / postgres.js as alternatives; the serverless driver docs define HTTP as one-shot/non-interactive and WebSockets as the path for session and interactive transaction support.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_72-DPvmpokHCOLV2eKPk1Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Drizzle + Neon: neon-http for serverless one-shots, neon-ws for transactions <span>— Vectle</span></a>