What driver should I use for Postgres in serverless environments?

Use Neon's `@neondatabase/serverless` driver instead of the standard `pg` driver, as the standard driver is not compatible with edge environments. For Drizzle, you can choose between `neon-http` for single queries over HTTP or `neon-serverless` WebSocket driver for transactions and sessions.

Can I use pooled connections for database migrations?

No, you should not use pooled connections for migrations. DDL operations fail through PgBouncer, so you must use the direct connection endpoint for running migrations.

How does Neon Postgres handle concurrent connections?

Neon uses PgBouncer connection pooling to handle concurrent connections, supporting up to 10,000 connections through the pooled endpoint. For Prisma, you configure dual connection strings with `DATABASE_URL` for pooled queries and `DIRECT_URL` for migrations.

What ORMs does this skill support?

This skill provides configuration patterns for both Prisma ORM and Drizzle ORM, with specific setup instructions and best practices for each.

How can I set up preview environments for pull requests?

You can use GitHub Actions with `neondatabase/create-branch-action@v5` to automatically create database branches for preview environments, enabling per-PR database instances using Neon's copy-on-write database branching feature.

Skill

Optimize Neon Postgres with Prisma and Drizzle

Name: Neon Postgres
Availability: OnlineOnly
Author: Antigravity

Patterns for Neon serverless Postgres: connection pooling, database branching, and Prisma/Drizzle integration.

Get skill

Works with postgresprismadrizzlegithub

Antigravity

Own this? Claim it

Spark score

out of 100

Updated last month

Version 13.1.0

Add to Favorites

Why it matters

Streamline your development workflow by implementing expert patterns for Neon serverless Postgres. This asset provides optimized configurations for Prisma and Drizzle ORMs, ensuring efficient connection pooling and database branching for enhanced development and testing.

Outcomes

What it gets done

Configure Prisma with Neon connection pooling and direct URL for migrations.

Integrate Drizzle ORM with Neon's serverless HTTP and WebSocket drivers.

Implement database branching strategies for development and CI/CD pipelines.

Avoid common anti-patterns for connection pooling and ORM usage with Neon.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-neon-postgres | bash

Overview

Neon Postgres

Expert patterns for Neon serverless Postgres: Prisma and Drizzle connection pooling with pooled vs direct URLs, instant copy-on-write database branching, Vercel preview-environment integration, and autoscaling/cold-start handling. Use it when connecting Prisma or Drizzle to Neon, setting up branching or PR-preview databases, or diagnosing cold-start latency and connection exhaustion.

What it does

Provides expert patterns for Neon serverless Postgres. Configures Prisma with two connection strings - a pooled DATABASE_URL (via PgBouncer, up to 10K connections) for the app and a DIRECT_URL for migrations, since DDL operations fail through the pooler - and Drizzle ORM with Neon's serverless driver, choosing between neon-http (fast single queries) and neon-serverless (WebSocket, needed for transactions). Documents PgBouncer's connection limits by compute size (0.25 CU gives 112 connections, up to 8 CU giving 3604), instant copy-on-write database branching for dev/test/preview environments via the Neon CLI or GitHub Actions, and Vercel preview-environment integration (Vercel-managed or Neon-managed, auto-creating a branch per PR). Covers autoscaling and cold-start behavior - 500ms to a few seconds of latency when waking from scale-to-zero - with retry-with-backoff code and a keep-alive ping pattern, and recommends disabling scale-to-zero in production. Of the pooler's connection budget, 7 connections are reserved for Neon's own superuser, further reducing what's actually available to the application. Prisma's own error codes P1001/P1002 signal exactly this connection-failure class, which is what the retry logic checks for.

npx prisma migrate dev

It also lists concrete anti-patterns with fixes (pooled connection for migrations, opening a new connection per request, HTTP driver for transactions, sharing one database across preview branches) and validation checks that flag them as ERROR or WARNING (exposed direct URLs in client code, hardcoded connection strings, missing sslmode=require, high pool size in serverless functions).

When to use - and when NOT to

Use it when connecting Prisma or Drizzle to Neon, setting up connection pooling, creating database branches for development or PR previews, integrating Neon with Vercel preview deployments, or diagnosing cold-start latency and connection-pool exhaustion in serverless environments.

Inputs and outputs

Input: a Neon project needing a Prisma/Drizzle connection setup, a branching or preview-environment workflow, or a cold-start/connection issue to diagnose. Output: .env and ORM schema configuration (pooled vs direct URLs), Neon CLI/GitHub Actions commands for branch create/list/delete, Vercel integration steps and vercel.json build-command wiring, and retry/keep-alive code for cold starts.

Integrations

Integrates Neon with Prisma (pooled DATABASE_URL plus direct DIRECT_URL), Drizzle ORM (neon-http/neon-serverless drivers), Vercel (preview-branch-per-PR, Vercel-managed or Neon-managed), and GitHub Actions (create-branch-action/delete-branch-action for branch lifecycle). Delegates to sibling skills for auth (clerk-auth), caching (redis-specialist), full-text search (algolia-search), event analytics (segment-cdp), and deployment (vercel-deployment).

Who it's for

Developers building on Neon serverless Postgres with Prisma or Drizzle who need correct pooling, branching, and preview-environment setup without hitting connection-limit or cold-start surprises.

FAQ

Common questions

Discussion