What Prisma Actually Does

Every Next.js + Postgres tutorial says “install Prisma.” You run npx prisma init, define some models, push to the database, and suddenly you can query data with TypeScript autocomplete. It feels like magic. But what is actually happening?

What It Actually Is

Prisma is an ORM — Object Relational Mapper. That's a fancy name for a translation layer. Your code thinks in JavaScript objects. Your database thinks in SQL rows and columns. Prisma sits in the middle and translates between the two.

Instead of writing SELECT * FROM users WHERE email = '[email protected]', you write prisma.user.findUnique({ where: { email: '[email protected]' } }). Prisma generates the SQL, sends it to the database, and returns a typed JavaScript object. You get autocomplete, type checking, and never write a SQL string.

The Problem It Solves

The Magic Trick Revealed

When you call prisma.user.findMany(), here's what actually happens:

  Your Code (TypeScript)
    │
    │  prisma.user.findMany({ where: { active: true } })
    │
    ▼
  Prisma Client (generated library)
    │  Translates JS method calls → SQL query
    │  Validates types at compile time
    │
    ▼
  Prisma Engine (Rust binary)
    │  Connection pooling
    │  Query optimization
    │  Runs the actual SQL
    │
    ▼
  Database (Postgres, MySQL, SQLite, etc.)
    │
    ▼
  SELECT * FROM "User" WHERE "active" = true;
    │
    ▼
  Result → typed JS object with full autocomplete ✓

The key insight: Prisma Client is generated code. Every time you change your schema and run prisma generate, it rebuilds a custom client library with types that match your exact database structure. That's why autocomplete works so well — it's not guessing, it's reading your schema.

The Schema File

Everything in Prisma starts with schema.prisma. This is your single source of truth for how your database looks. It defines your models (tables), fields (columns), relations, and which database you're connecting to.

// prisma/schema.prisma

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

generator client {
  provider = "prisma-client-js"
}

model User {
  id        String   @id @default(cuid())
  email     String   @unique
  name      String?
  posts     Post[]
  createdAt DateTime @default(now())
}

model Post {
  id        String   @id @default(cuid())
  title     String
  content   String?
  author    User     @relation(fields: [authorId], references: [id])
  authorId  String
  published Boolean  @default(false)
}

This isn't SQL. It's Prisma's own schema language. From this single file, Prisma generates your TypeScript types, your database migrations, and your query client. Change this file and everything else updates to match.

The 3 Commands You Actually Need

The Honest Catch: Cold Start Latency

When NOT to Use Prisma

The Alternatives