GraphQL Server (SDL first) Example with hapi & Prisma Postgres

This example shows how to implement an GraphQL Server Example with Hapi (SDL first) with the following stack:

hapi: Web framework with a focus on security and scalability
Apollo Server Integration for Hapi
Prisma Client: Databases access (ORM)
Prisma Migrate: Database migrations
Prisma Postgres: A serverless PostgreSQL database built on unikernels.

Getting started

1. Download example and navigate into the project directory

Download this example:

npx try-prisma@latest --template orm/hapi-graphql-sdl-first --install npm --name hapi-graphql-sdl-first

Then, navigate into the project directory:

cd hapi-graphql-sdl-first

Alternative: Clone the entire repo

Clone this repository:

git clone git@github.com:prisma/prisma-examples.git --depth=1

Install npm dependencies:

cd prisma-examples/orm/hapi-graphql-sdl-first
npm install

2. Create and seed the database

Create a new Prisma Postgres database by executing:

npx prisma init --db

If you don't have a Prisma Data Platform account yet, or if you are not logged in, the command will prompt you to log in using one of the available authentication providers. A browser window will open so you can log in or create an account. Return to the CLI after you have completed this step.

Once logged in (or if you were already logged in), the CLI will prompt you to:

Select a region (e.g. us-east-1)
Enter a project name

After successful creation, you will see output similar to the following:

CLI output

Let's set up your Prisma Postgres database!
? Select your region: ap-northeast-1 - Asia Pacific (Tokyo)
? Enter a project name: testing-migration
✔ Success! Your Prisma Postgres database is ready ✅

We found an existing schema.prisma file in your current project directory.

--- Database URL ---

Connect Prisma ORM to your Prisma Postgres database with this URL:

prisma+postgres://accelerate.prisma-data.net/?api_key=...

--- Next steps ---

Go to https://pris.ly/ppg-init for detailed instructions.

1. Install and use the Prisma Accelerate extension
Prisma Postgres requires the Prisma Accelerate extension for querying. If you haven't already installed it, install it in your project:
npm install @prisma/extension-accelerate

...and add it to your Prisma Client instance:
import { withAccelerate } from "@prisma/extension-accelerate"

const prisma = new PrismaClient().$extends(withAccelerate())

2. Apply migrations
Run the following command to create and apply a migration:
npx prisma migrate dev

3. Manage your data
View and edit your data locally by running this command:
npx prisma studio

...or online in Console:
https://console.prisma.io/{workspaceId}/{projectId}/studio

4. Send queries from your app
If you already have an existing app with Prisma ORM, you can now run it and it will send queries against your newly created Prisma Postgres instance.

5. Learn more
For more info, visit the Prisma Postgres docs: https://pris.ly/ppg-docs

Locate and copy the database URL provided in the CLI output. Then, create a .env file in the project root:

touch .env

Now, paste the URL into it as a value for the DATABASE_URL environment variable. For example:

# .env
DATABASE_URL=prisma+postgres://accelerate.prisma-data.net/?api_key=ey...

Run the following command to create tables in your database. This creates the User and Post tables that are defined in prisma/schema.prisma:

npx prisma migrate dev --name init

Execute the seed file in prisma/seed.ts to populate your database with some sample data, by running:

npx prisma db seed

3. Start the GraphQL server

Launch your GraphQL server with this command:

npm run dev

Navigate to http://localhost:4000/graphql in your browser to explore the API of your GraphQL server in a GraphQL Playground.

Using the GraphQL API

The schema that specifies the API operations of your GraphQL server is defined in ./schema.graphql. Below are a number of operations that you can send to the API using the GraphQL Playground.

Feel free to adjust any operation by adding or removing fields. The GraphQL Playground helps you with its auto-completion and query validation features.

Retrieve all published posts and their authors

query {
  feed {
    id
    title
    content
    published
    author {
      id
      name
      email
    }
  }
}

See more API operations

Retrieve the drafts of a user

{
  draftsByUser(
    userUniqueInput: {
      email: "mahmoud@prisma.io"
    }
  ) {
    id
    title
    content
    published
    author {
      id
      name
      email
    }
  }
}

Create a new user

mutation {
  signupUser(data: { name: "Sarah", email: "sarah@prisma.io" }) {
    id
  }
}

Create a new draft

mutation {
  createDraft(
    data: { title: "Join the Prisma Discord", content: "https://pris.ly/discord" }
    authorEmail: "alice@prisma.io"
  ) {
    id
    viewCount
    published
    author {
      id
      name
    }
  }
}

Publish/unpublish an existing post

mutation {
  togglePublishPost(id: __POST_ID__) {
    id
    published
  }
}

Note that you need to replace the __POST_ID__ placeholder with an actual id from a Post record in the database, e.g.5:

mutation {
  togglePublishPost(id: 5) {
    id
    published
  }
}

Increment the view count of a post

mutation {
  incrementPostViewCount(id: __POST_ID__) {
    id
    viewCount
  }
}

Note that you need to replace the __POST_ID__ placeholder with an actual id from a Post record in the database, e.g.5:

mutation {
  incrementPostViewCount(id: 5) {
    id
    viewCount
  }
}

Search for posts that contain a specific string in their title or content

{
  feed(
    searchString: "prisma"
  ) {
    id
    title
    content
    published
  }
}

Paginate and order the returned posts

{
  feed(
    skip: 2
    take: 2
    orderBy: { updatedAt: desc }
  ) {
    id
    updatedAt
    title
    content
    published
  }
}

Retrieve a single post

{
  postById(id: __POST_ID__ ) {
    id
    title
    content
    published
  }
}

Note that you need to replace the __POST_ID__ placeholder with an actual id from a Post record in the database, e.g.5:

{
  postById(id: 5 ) {
    id
    title
    content
    published
  }
}

Delete a post

mutation {
  deletePost(id: __POST_ID__) {
    id
  }
}

Note that you need to replace the __POST_ID__ placeholder with an actual id from a Post record in the database, e.g.5:

mutation {
  deletePost(id: 5) {
    id
  }
}

Evolving the app

Evolving the application typically requires two steps:

Migrate your database using Prisma Migrate
Update your application code

For the following example scenario, assume you want to add "profile" feature to the app where users can create a profile and write a short bio about themselves.

1. Migrate your database using Prisma Migrate

The first step is to add a new table, e.g. called Profile, to the database. You can do this by adding a new model to your Prisma schema file file and then running a migration afterwards:

// ./prisma/schema.prisma

model User {
  id      Int      @default(autoincrement()) @id
  name    String?
  email   String   @unique
  posts   Post[]
+ profile Profile?
}

model Post {
  id        Int      @id @default(autoincrement())
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  title     String
  content   String?
  published Boolean  @default(false)
  viewCount Int      @default(0)
  author    User?    @relation(fields: [authorId], references: [id])
  authorId  Int?
}

+model Profile {
+  id     Int     @default(autoincrement()) @id
+  bio    String?
+  user   User    @relation(fields: [userId], references: [id])
+  userId Int     @unique
+}

Once you've updated your data model, you can execute the changes against your database with the following command:

npx prisma migrate dev --name add-profile

This adds another migration to the prisma/migrations directory and creates the new Profile table in the database.

2. Update your application code

You can now use your PrismaClient instance to perform operations against the new `Profile table. Those operations can be used to implement queries and mutations in the GraphQL API

2.1 Add the `Profile` type to your GraphQL schema

First, add a new GraphQL type to your existing typeDefs:

// ./src/schema.ts

+type Profile {
+  id: ID!
+  bio: String
+  user: User
+}

type User {
  email: String!
  id: ID!
  name: String
  posts: [Post!]!
+  profile: Profile
}

Don't forget to include Profile and update User root types in the resolvers object

const resolvers ={
  Query: { /** as before */ },
  Mutation: { /** as before */ },
  DateTime: DateTimeResolver,
  Post: { /** as before */ },
  User: {
    posts: (parent, _args, context: Context) => {
      return context.prisma.user.findUnique({
        where: { id: parent?.id }
      }).posts()
    },
+    profile: (parent, _args, context: Context) => {
+      return context.prisma.profile.findUnique({
+        where: { userId: parent?.id }
+      })
+    }
  },
+  Profile: {
+    user: (parent, _args, context: Context) => {
+      const profile = await context.prisma.profile.findUnique({
+        where: { id: parent?.id },
+         include: { user: true }
+        })
+       return profile.user
+    }
+  }
}

2.2 Add a `createProfile` GraphQL mutation

// ./src/schema.ts

const typeDefs = `
// other types

type Mutation {
  createDraft(authorEmail: String!, data: PostCreateInput!): Post
  deletePost(id: Int!): Post
  incrementPostViewCount(id: Int!): Post
  signupUser(data: UserCreateInput!): User!
  togglePublishPost(id: Int!): Post
+  addProfileForUser(bio: String, userUniqueInput: UserUniqueInput): Profile
}
`

const resolvers ={
  Query: { /** as before */ },
  Mutation: {
    // other mutations

+    addProfileForUser: (_parent, args: { userUniqueInput: UserUniqueInput, bio: string }, context: Context) => {
+      return context.prisma.profile.create({
+        data: {
+          bio: args.bio,
+          user: {
+            connect: {
+              id: args.userUniqueInput?.id,
+              email: args.userUniqueInput?.email
+            }
+          }
+        }
+      })
+    }
  },
  DateTime: DateTimeResolver,
  Post: { /** as before */ },
  User: { /** as before */},
  Profile: { /** as before */  }
}

Finally, you can test the new mutation like this:

mutation {
  addProfileForUser(
    userUniqueInput: {
      email: "mahmoud@prisma.io"
    }
    bio: "I like turtles"
  ) {
    id
    bio
    user {
      id
      name
    }
  }
}

Expand to view more sample Prisma Client queries on Profile

Here are some more sample Prisma Client queries on the new Profile model:

Create a new profile for an existing user

const profile = await prisma.profile.create({
  data: {
    bio: 'Hello World',
    user: {
      connect: { email: 'alice@prisma.io' },
    },
  },
})

Create a new user with a new profile

const user = await prisma.user.create({
  data: {
    email: 'john@prisma.io',
    name: 'John',
    profile: {
      create: {
        bio: 'Hello World',
      },
    },
  },
})

Update the profile of an existing user

const userWithUpdatedProfile = await prisma.user.update({
  where: { email: 'alice@prisma.io' },
  data: {
    profile: {
      update: {
        bio: 'Hello Friends',
      },
    },
  },
})

Switch to another database (e.g. SQLite, MySQL, SQL Server, MongoDB)

If you want to try this example with another database than Postgres, you can adjust the the database connection in prisma/schema.prisma by reconfiguring the datasource block.

Learn more about the different connection configurations in the docs.

Expand for an overview of example configurations with different databases

Remove the Prisma Client extension

Before you proceed to use your own database, you should remove the Prisma client extension required for Prisma Postgres:

npm uninstall @prisma/extension-accelerate

Remove the client extension from your PrismaClient instance:

- const prisma = new PrismaClient().$extends(withAccelerate())
+ const prisma = new PrismaClient()

Your own PostgreSQL database

To use your own PostgreSQL database remove the @prisma/extension-accelerate package and remove the Prisma client extension.

SQLite

Modify the provider value in the datasource block in the prisma.schema file:

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

Create an .env file and add the SQLite database connection string in it. For example:

DATABASE_URL="file:./dev.db""

MySQL

Modify the provider value in the datasource block in the prisma.schema file:

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

Create an .env file and add a MySQL database connection string in it. For example:

## This is a placeholder url
DATABASE_URL="mysql://janedoe:mypassword@localhost:3306/notesapi"

Microsoft SQL Server

Modify the provider value in the datasource block in the prisma.schema file:

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

Create an .env file and add a Microsoft SQL Server database connection string in it. For example:

## This is a placeholder url
DATABASE_URL="sqlserver://localhost:1433;initial catalog=sample;user=sa;password=mypassword;"

MongoDB

Modify the provider value in the datasource block in the prisma.schema file:

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

Create an .env file and add a local MongoDB database connection string in it. For example:

## This is a placeholder url
DATABASE_URL="mongodb://USERNAME:PASSWORD@HOST/DATABASE?authSource=admin&retryWrites=true&w=majority"

Next steps

Check out the Prisma docs
Join our community on Discord to share feedback and interact with other users.
Subscribe to our YouTube channel for live demos and video tutorials.
Follow us on X for the latest updates.
Report issues or ask questions on GitHub.