Prisma Web Documentation Ecosystem

The Prisma Blog is a Next.js application that hosts product updates, announcements, tutorials, and technical posts. Key features include:

• Blog posts: MDX-based articles featuring authors, dates, hero images, and code examples.
• Search: Full-text search functionality over the blog content.
• LLM endpoints: Specialized routes designed for AI/LLM consumption of processed blog text, accessible via /llms.mdx/... and /llms-full.txt.

Prisma ORM is an open-source toolkit for Node.js and TypeScript that provides type-safe database access, migrations, and a visual data editor. It consists of three main components:

• Prisma Client: An auto-generated, type-safe ORM interface for querying your database.
• Prisma Migrate: A database migration system for managing schema changes.
• Prisma Studio: A GUI for viewing and editing your data.

Prisma is designed to provide type-safe queries validated at compile time, allowing you to think in objects while maintaining a single source of truth in your Prisma schema.

The Eclipse Design System documentation site is a Next.js application that serves as the reference for the @prisma/eclipse component library. It provides:

• Design system documentation: Interactive documentation for Eclipse atoms (e.g., Button, Badge, Input) and molecules (e.g., Card, Tabs, CodeBlock).
• Component playground: Live, editable examples for each component to test usage and styles.
• Reference site: Acts as the primary component library reference, whereas the main Prisma documentation (apps/docs) consumes these components for its own UI.

This guide demonstrates how to build a type-safe GraphQL API by synchronizing types across the ORM, GraphQL object types, GraphQL query types, and resolvers using Prisma's generated types and the Pothos Prisma plugin.

Key components used in this workflow include:

• GraphQL Yoga: For setting up the GraphQL server.
• Pothos: For the schema builder.
• Prisma Client: For querying data.
• Pothos Prisma Plugin: To bridge Prisma types with GraphQL types.

Prisma Postgres and Neon are both serverless Postgres services. Key differences include:

• Query Caching: Prisma Postgres has built-in query-level caching via Prisma Accelerate. Neon requires external services (e.g., Redis, Upstash).
• Database Branching: Neon supports instant, storage-efficient database branching. Prisma Postgres does not currently support branching.
• Connection Pooling: Both use PgBouncer in transactional mode. Prisma Postgres uses tenant-isolated instances, while Neon uses shared infrastructure with logical isolation per user-database pair.
• Edge/Serverless Support: Both support HTTP-based drivers for environments like Cloudflare Workers and Vercel Edge Functions.
• Pricing: Prisma Postgres bills based on operations and storage. Neon bills based on compute hours and storage.

The awesome-links application is a Next.js project with the following key directories and responsibilities:

• components/: UI components like Layout and AwesomeLink.
• graphql/: GraphQL schema (schema.graphql), types, and context.
• lib/: Shared utilities like apollo.ts and prisma.ts.
• pages/: Next.js routes:
  • index.tsx: Main page with paginated links.
  • link/[id].tsx: Individual link details and bookmarking.
  • admin.tsx: Admin-only page for creating links.
  • favorites.tsx: User's bookmarked links.
  • api/graphql.ts: The GraphQL endpoint.
  • api/auth/[...auth0].ts: Auth0 authentication handler.
  • api/auth/hook.ts: Handles creating user records in the database.
• prisma/: Database schema, migrations, and seeding logic.
• public/: Static assets.

The project is a Next.js application with the following key directories and files:

• components/: UI components like Layout and AwesomeLink.tsx.
• graphql/: Contains GraphQL schema definitions (schema.ts), type definitions, and the Pothos builder (builder.tsx).
• lib/: Utility modules including apollo.ts (Apollo Client) and prisma.ts (Prisma Client).
• pages/: Next.js routing files:
  • index.tsx: The main page that fetches and displays paginated links.
  • _app.tsx: The root component for layout and state persistence.
  • api/graphql.ts: The Next.js API route serving as the GraphQL endpoint.
• prisma/: Database configuration, including schema.prisma, migrations, and seed.ts.
• public/: Static assets.
• styles/: TailwindCSS configuration and styles.

This series demonstrates how to build a production-ready backend using TypeScript, PostgreSQL, and Prisma. The workflow covers:

• Data Modeling: Using Prisma Schema as the single source of truth.
• API Development: Building a REST API with Hono.
• Security: Implementing passwordless authentication and authorization.
• CI/CD: Configuring GitHub Actions to spin up a throwaway PostgreSQL database, apply migrations, and run tests on every push.
• Deployment: Deploying to Prisma Compute using the Prisma CLI and enabling automatic deployment via Git integration.
• Database Management: Leveraging Prisma Postgres to run the app next to the database, avoiding separate database add-ons and connection-churn issues.

The prisma migrate command group is used to manage database migrations, allowing you to create, apply, and inspect schema changes.

Note: Prisma Migrate does not support MongoDB. For MongoDB, use db push instead.

prisma migrate [command] [options]

This repository is a pnpm monorepo organized as follows: