Building Production-Ready REST APIs with Next.js 16 and Prisma

In this tutorial, we will construct a production-ready REST API using Next.js 16 App Router, TypeScript, and Prisma ORM. When designing endpoints for high-performance publishing systems, security and query efficiency are paramount.

Designing the Schema

Let's look at the database schema. In schema design, index planning is crucial to keep read times under 50ms. Here is how we define the post model:

model Post {
  id          String     @id @default(uuid())
  title       String
  slug        String     @unique
  excerpt     String     @db.Text
  content     String     @db.Text
  views       Int        @default(0)
  createdAt   DateTime   @default(now())

  @@index([slug])
}

Implementing Server Actions

Server Actions in Next.js 16 provide a seamless way to trigger backend operations without spinning up full HTTP endpoints. Here is a simple Server Action to create a subscriber:

"use server";

import { prisma } from "@/lib/db";
import { z } from "zod";

const schema = z.object({
  email: z.string().email(),
});

export async function addSubscriber(formData: FormData) {
  const email = formData.get("email") as string;
  const parsed = schema.safeParse({ email });
  
  if (!parsed.success) {
    return { error: "Invalid Email" };
  }

  await prisma.newsletterSubscriber.create({
    data: { email: email.toLowerCase() }
  });

  return { success: true };
}

Performance Tuning

When working with PostgreSQL, use indexes appropriately. For lookups on slug columns, an index is mandatory:

• Query optimization prevents full table scans.
• Enable connection pooling on Supabase for serverless functions using port 6543 (PgBouncer).
• Use dynamic ISR caching to revalidate static pages when new entries are published.