neon-drizzle

Install drizzle-orm and @neondatabase/serverless, provision a Neon database to get a DATABASE_URL connection string, create a drizzle.config.ts with explicit dotenv loading, define your schema, then run drizzle-kit generate and migrate to apply tables.

Use the HTTP adapter for serverless and edge environments like Vercel, Cloudflare Workers, and AWS Lambda. Use the WebSocket adapter for long-lived Node.js servers like Express or Fastify when you need transactions, prepared statements, and connection pooling.

Yes, Drizzle can coexist with Prisma, TypeORM, or other ORMs. Create an isolated src/drizzle directory, use it for new tables first, then gradually mirror existing tables and migrate queries over time without disrupting current functionality.

This happens because drizzle-kit runs as a separate process and does not inherit environment variables automatically. Fix it by adding dotenv config with an explicit path like config({ path: '.env.local' }) at the top of drizzle.config.ts before exporting the configuration.

No, the HTTP adapter does not support transactions, prepared statements, or streaming. Use batch operations for multiple writes, or switch to the WebSocket adapter with a connection pool if your application requires atomic transactions.

Drizzle generates renames as a drop plus add, which deletes data. After running drizzle-kit generate, manually edit the migration SQL to use ALTER TABLE RENAME COLUMN instead, then apply the migration normally.