neon-postgres

Neon's HTTP driver lets serverless functions query PostgreSQL directly over HTTP without maintaining persistent connections. Install @neondatabase/serverless, configure your Neon DATABASE_URL, and call neon(process.env.DATABASE_URL) for edge and one-shot workloads that don't need pooling overhead.

Yes. Neon's WebSocket pool driver supports transactions, connection pooling, and long-running operations for full-stack backends. Use new Pool({ connectionString: process.env.DATABASE_URL }) when you need stateful connections beyond single HTTP requests.

Neon branching creates isolated database copies for feature testing without affecting production. The skill covers running migrations safely across branches and environments, letting you ship features with autoscaling enabled across multiple deployment targets.

No. Drizzle ORM is optional. The skill works with raw queries using the @neondatabase/serverless package alone. Drizzle integration is available if you prefer an ORM, but it's not required to query Neon over HTTP or WebSocket drivers.

HTTP drivers suit edge functions and stateless queries with low latency; WebSocket drivers maintain pooled connections for transactions and long-running operations. Choose HTTP for serverless frontends and WebSocket for backends needing persistent state.

Yes. Neon autoscaling adjusts compute resources based on demand. The skill covers configuring autoscaling alongside branching and migrations so your app handles traffic spikes without manual intervention across development, staging, and production branches.