cloudflare-hyperdrive

Cloudflare Hyperdrive connects Workers to PostgreSQL and MySQL databases using global connection pooling and edge caching. Create a Hyperdrive config with `wrangler hyperdrive create`, bind it in wrangler.jsonc, then query via `env.HYPERDRIVE.connectionString` using supported drivers like pg, postgres.js, or mysql2.

Global connection pooling eliminates repeated handshake overhead, and edge-enabled query caching automatically stores read-mostly results. Hyperdrive applies both strategies across multiple regions, dramatically reducing latency for Cloudflare Workers accessing remote databases.

Yes. Hyperdrive supports driver integrations including Prisma ORM and Drizzle ORM alongside native drivers (pg, postgres.js, mysql2), enabling ORMs to query through the pooled, cached connection layer without modification.

Configure TLS/SSL for encrypted connections and use Cloudflare Tunnel to secure private database access. Hyperdrive's wrangler binding workflow handles the connection setup, allowing Workers to reach on-premises or VPC-isolated databases safely.

Hyperdrive connects Cloudflare Workers to PostgreSQL and MySQL databases. It does not support other database engines, but covers the most common relational databases used in production migrations to edge-proxied, cached architectures.

Minimal changes required. Hyperdrive integrates via standard database drivers (pg, postgres.js, mysql2) and ORMs (Prisma, Drizzle), so existing query logic works unchanged—only the connection string source shifts to the Hyperdrive binding.