A Simple Analogy

Prisma on the edge is like having a database agent in every city. Reduced latency, better performance globally.

---

Why Edge Deployment?

• Latency: Database closer to users
• Performance: Reduced round-trips
• Cost: Serverless pricing
• Scalability: Automatic scaling
• Global: Reach worldwide users

---

Edge Database Providers

- Vercel Postgres
- Neon (Serverless PostgreSQL)
- PlanetScale (MySQL Serverless)
- Turso (SQLite)
- Cloudflare D1 (SQLite)

---

Setup with Vercel Postgres

# Install Vercel CLI
npm i -g vercel

# Create database
vercel postgres create

# Get connection string
vercel env pull .env.local

datasource db {
  provider = "postgresql"
  url      = env("POSTGRES_PRISMA_URL")
}

---

Serverless Functions

// api/users.ts (Vercel Function)
import { prisma } from '@/lib/prisma';

export const config = {
  runtime: 'nodejs',
};

export default async function handler(req, res) {
  const users = await prisma.user.findMany();
  res.status(200).json(users);
}

---

Connection Pooling

// Use connection pooling for serverless
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

// Connection string with pooling
postgres://user:pass@pool.neon.tech/db?sslmode=require

---

Best Practices

1. Pooling: Essential for serverless
2. Timeout: Set appropriate limits
3. Caching: Cache responses
4. Batch: Group operations
5. Monitoring: Track connection usage

---

Related Concepts

• Serverless architecture
• Connection pooling
• Edge computing
• Distributed databases

---

Summary

Deploy Prisma to edge platforms like Vercel Postgres or Neon for global, serverless database access.