Build a Complete CRUD gRPC API with Node.js and Express 2025

Google Remote Procedure Call, also commonly referred to as gRPC is a modern, open-source, high-performance remote procedure call (RPC) framework that is frequently used in microservice architectures to connect small independent services in and across data centers efficiently.

gRPC is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services. https://www.grpc.io/

What is an RPC (Remote Procedure Call) framework? RPC is a distributed computing technique that a program can use to execute a piece of code running on the same or a remote machine. The procedure call is commonly referred to as a function call or a subroutine call.

In this guide, you will learn how to build a complete CRUD gRPC API server and client with TypeScript in a Node.js environment that runs on an Expressjs framework and uses a Prisma database ORM. We’ll create five RPC services on the gRPC server that are going to be evoked by the gRPC client to perform the basic CRUD (Create, Read, Update, and Delete) operations.

To do this, we will create three .proto files that will hold the Protobuf definitions to create a new record, update the existing record, and the RPC response.

Next, we’ll create the services.proto file to define the RPC methods or services that will be evoked by the gRPC client.

More practice:

Build a Complete CRUD gRPC API with Node.js and Express

Prerequisites

Before you begin this tutorial:

Software

Have a working Node.js development environment. Visit the official Node.js website to download the latest or the LTS (Long Term Support) version.
A basic understanding of Prisma, and how to use a PostgreSQL GUI client will be beneficial.
Have the latest version of Docker installed on your system.

VS Code Extensions

DotENV – This extension provides syntax highlighting for the configuration files ending with .env extension.
Proto3 – This extension uses the Protobuf compiler under the hood to provide syntax highlighting, syntax validation, line and block comments, compilation, code snippets, code completion, and code formatting for all files ending with .proto extension.
You can download and install the right Protocol buffer compiler binary executable for your operating system from the gRPC website.
MySQL – This VS Code database client will enable you to access and mutate the data stored in any supported database including PostgreSQL.

By default, the Protobuf compiler searches for the .proto files in the root directory so we need to manually tell it the location of the proto files.

To do this, press CTRL + , to open the settings page and search for Proto3. Then, click on the Edit in settings.json link and add this option to the Protoc configuration.


{
"protoc": {
  "options": ["--proto_path=proto"]
  }
}

Node.js gRPC Server and Client Overview

Here, we will use an API testing tool to make HTTP requests to the Node.js Express server. The request will then be delegated to the right controller which will in tend call the appropriate gRPC client method.

The gRPC client will then go ahead and evoke the right RPC service on the Node.js gRPC API and return the result to the Express controller. Finally, the Express server will return the result in JSON format to the user or client.

To have access to the same Postman collection used in testing the Node.js gRPC API, click on the Postman Collection link, and copy the JSON document.

Next, click on the import button in your Postman software, choose the “Raw text” option, and paste the JSON document.

Then, click on the Continue button to move to the next screen before clicking the Import button to add the collection.

Calling the Create Record RPC Service

To add a new record to the database, the client or user will make a POST request to the localhost:8080/api/posts endpoint on the Node.js express server. The Express server will then route the request to the right controller where the gRPC client will evoke the CreatePost RPC service on the gRPC server to add the new record to the database.

Next, the newly-created record returned to the gRPC client will be sent to the user or the client in JSON format.

Calling the Update Record RPC Service

To update an existing record in the database, a PATCH request will be made to the localhost:8080/api/posts/:postId endpoint with the payload in the request body. The gRPC client will then evoke the UpdatePost RPC method on the gRPC server to edit the record in the database.

Calling the Get Single Record RPC Service

Similar to the update operation, a GET request will be made to the localhost:8080/api/posts/:postId endpoint with the ID of the record included in the request URL.

The Express server will then route the request to the right handler where the gRPC client will evoke the GetPost RPC method to return the record that matches the query.

nodejs grpc crud api get a single document

Calling the Delete Record RPC Service

Here, a DELETE request will be made to the localhost:8080/api/posts/:postId endpoint to remove the record that matches the provided ID from the database.

Calling the Get All Records RPC Service

All the above operations fall under Unary RPC. To retrieve a list of records from the database, we’ll use the server-side streaming RPC method instead of Unary RPC.

So a GET request will be made to the localhost:8080/api/posts endpoint where the GetPosts RPC service will be evoked to stream the records to the gRPC client.

Next, we will then listen to the “data” event emitted by the gRPC client and push the returned documents into an array before returning it to the client in JSON format.

nodejs grpc crud api retrieve all documents

Step 1: Setup and Installation

To begin, create a new folder and open it with your preferred IDE or text editor. You can name it grpc-node-prisma .

mkdir grpc-node-prisma && cd grpc-node-prisma && code .

Next, initialize the Node.js TypeScript project with the following commands:


yarn init -y && yarn add -D typescript && yarn tsc --init
# or
npx init -y && npx install -D typescript && npx tsc --init

This gRPC API example is based on a PostgreSQL database, however, you can use any database server supported by Prisma.

Now to set up the Postgres database, we will use Docker because it’s easier to set up and maintain. To do that, create a docker-compose.yml file in the root directory and add the following code.

docker-compose.yml


version: '3'
services:
  postgres:
    image: postgres
    container_name: postgres
    ports:
      - '6500:5432'
    restart: always
    env_file:
      - ./.env
    volumes:
      - postgres-db:/var/lib/postgresql/data
volumes:
  postgres-db:

The above configuration will pull the latest Postgres image from Docker Hub, build the image, run the Postgres server in a Docker container, and map port 6500 to the default Postgres port.

Since we used placeholders for the Postgres credentials in the docker-compose.yml file, create a .env file in the root directory and add the following environment variables.

.env


DATABASE_PORT=6500
POSTGRES_PASSWORD=password123
POSTGRES_USER=postgres
POSTGRES_DB=grpc-node-prisma
POSTGRES_HOST=postgres
POSTGRES_HOSTNAME=127.0.0.1

Now run this command to start the Postgres Docker container:


docker-compose up -d

Stop the Docker container with this command:


docker-compose down

Step 2: Create the Protobuf Messages

Before we can generate the TypeScript files with the Protobuf compiler, we first need to create the Protobuf messages and RPC services using the protocol buffer language.

One recommendation is to put all the Protobuf files in one folder. This will enable us to generate the gRPC server and client interfaces easily.

To do that, create a proto folder in the root directory to hold all the Protocol buffer files.

Next, create a proto/post.proto file and add the following Protobuf messages:

proto/post.proto


syntax = "proto3";

import "google/protobuf/timestamp.proto";

message Post {
  string id = 1;
  string title = 2;
  string content = 3;
  string category = 4;
  string image = 5;
  bool published = 6;
  google.protobuf.Timestamp created_at = 7;
  google.protobuf.Timestamp updated_at = 8;
}

message PostResponse { Post post = 1; }

Quite a lot happening in the above, let’s break it down. First, we specified the version of the Protobuf language on the first line of the file – in this case, we used proto3.

Since the Timestamp type is not included in the built-in Protobuf types, we imported it from the Google standard library. This library contains popular data types not included in the Porotobuf built-in types.

To define a Protobuf field, we specified the data type followed by the field name and a unique identifier. The gRPC framework will use the unique identifier under the hood to identify the fields in the message binary format.

The unique identifier or number can range from 1 to 2047. The number between 1 and 15 will take one byte to encode, whereas the numbers ranging from 16 to 2047 will take two bytes to encode.

So it’s recommended to use field numbers between 1 to 15 if possible. This will reduce the size of the Protobuf message.

Visit the Protocol Buffer Encoding website to learn more.

With that out of the way, let’s create the Protobuf message to contain the fields required to add a new record to the database.

proto/rpc_create_post.proto


syntax = "proto3";

package post;

message CreatePostRequest {
  string title = 1;
  string content = 2;
  string category = 3;
  string image = 4;
  bool published = 5;
}

In the above, we used the package keyword provided by proto3 to define a package name for the Protobuf message.

proto/rpc_update_post.proto


syntax = "proto3";

package post;

message UpdatePostRequest {
  string id = 1;
  optional string title = 2;
  optional string content = 3;
  optional string category = 4;
  optional string image = 5;
  optional bool published = 6;
}

The above Protobuf message is similar to the CreatePostRequest message except that we used the optional keyword on the optional fields.

Step 3: Create the gRPC Services

Now that we have the Protobuf messages defined, let’s create a proto/services.proto file to contain the RPC definitions.

Since we have some of the Protobuf messages defined in other files, we will use the import keyword to include those files.

Here, we will create four Unary gRPC services and a Server streaming RPC service. The Server streaming gRPC method will allow us to stream the list of records retrieved from the database to the gRPC client.

Alternatively, we can use the repeated keyword on the field specified in the Protobuf response message to indicate that it’s an array of records. This approach will work but it’s considered bad practice.

proto/services.proto


syntax = "proto3";

import "post.proto";
import "rpc_create_post.proto";
import "rpc_update_post.proto";

// Post Service
service PostService {
  rpc CreatePost(CreatePostRequest) returns (PostResponse) {}
  rpc GetPost(PostRequest) returns (PostResponse) {}
  rpc GetPosts(GetPostsRequest) returns (stream Post) {}
  rpc UpdatePost(UpdatePostRequest) returns (PostResponse) {}
  rpc DeletePost(PostRequest) returns (DeletePostResponse) {}
}

message GetPostsRequest {
  int64 page = 1;
  int64 limit = 2;
}

message PostRequest { string id = 1; }

message DeletePostResponse { bool success = 1; }

CreatePost – This Unary RPC method will be evoked to add a new record to the database.
GetPost – This Unary RPC service will be evoked to return a single record from the database.
GetPosts – This Server streaming RPC service will be evoked to return a stream of the found records.
UpdatePost – This Unary RPC service will be evoked to update a record in the database.
DeletePost – This Unary RPC method will be evoked to remove a record from the database.

Before we can use gRPC in Node.js, we need to install these two dependencies to help us load the Protobuf files and set up the gRPC server and client.


yarn add @grpc/grpc-js @grpc/proto-loader

@grpc/grpc-js – This library contains the gRPC implementation for Nodejs.
@grpc/proto-loader – This library contains helper functions for loading .proto files.

Next, let’s create a bash script to help us generate the TypeScript files from the defined Protobuf files.

proto-gen.sh


#!/bin/bash

rm -rf pb/
yarn proto-loader-gen-types --longs=String --enums=String --defaults --keepCase --oneofs --grpcLib=@grpc/grpc-js --outDir=pb/ proto/*.proto

If by any chance the TypeScript files are not being generated then run the individual commands directly in the terminal.

When you run the above script, the @grpc/proto-loader package will generate the TypeScript files and output the results into a pb/ folder.

generated gRPC typescript files in nodejs

Now run the bash script to generate the TypeScript files with this command:


./proto-gen.sh

Step 4: Model the API Data with Prisma

Prisma is basically an ORM for TypeScript and Node.js. The code in this project can be adapted to work with any database server supported by Prisma.

First things first, let’s install the Prisma CLI and the Client:


yarn add -D prisma && yarn add @prisma/client
# or
npm install -D prisma && npm install @prisma/client

Now let’s run the Prisma init command with the --datasource-provider flag to generate the schema file.


mkdir server && cd server && yarn prisma init --datasource-provider postgresql
# or
mkdir server && cd server && npx prisma init --datasource-provider postgresql

The above command will generate prisma/schema.prisma , .gitignore , and .env files in the server folder.

Now delete the .gitignore , and .env files from the server folder.

Next, add the PostgreSQL connection URL to the .env file in the root directory. The DATABASE_URL will be used by Prisma behind the scene to create connection pools between the Node.js app and the Postgres server.


DATABASE_PORT=6500
POSTGRES_PASSWORD=password123
POSTGRES_USER=postgres
POSTGRES_DB=grpc-node-prisma
POSTGRES_HOST=postgres
POSTGRES_HOSTNAME=127.0.0.1

DATABASE_URL="postgresql://postgres:password123@localhost:6500/grpc-node-prisma?schema=public"

Now let’s define the API data structure with Prisma. Open the server/prisma/schema.prisma file and add the following schema definition.


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

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

model Post {
  id         String   @id @default(uuid())
  title      String   @unique @db.VarChar(255)
  content    String
  category   String
  image      String
  published  Boolean  @default(false)
  created_at DateTime @default(now())
  updated_at DateTime @updatedAt

  @@map(name: "posts")
}

In the above, we defined a Post model which will be transformed by the Prisma engine into an SQL table.

Add the following scripts to the package.json file:


{
"scripts": {
    "db:migrate": "npx prisma migrate dev --name post-entity --create-only --schema ./server/prisma/schema.prisma",
    "db:generate": " npx prisma generate --schema ./server/prisma/schema.prisma",
    "db:push": "npx prisma db push --schema ./server/prisma/schema.prisma"
  },
}

db:migrate – This command will create the database migration file without applying it.
db:generate – This command will generate the Prisma client.
db:push – This command will push the migration file to the database and keep the Prisma schema in sync with the database schema.

With that said, run this command to create the migration file and push the changes to the database.

Make sure the PostgreSQL Docker container is running


yarn db:migrate && yarn db:generate && yarn db:push
# or
npm run db:migrate && npm run db:generate && npm run db:push

Open any Postgres client and sign in with the credentials provided in the .env file to see the SQL table added by the Prisma CLI.

Next, let’s create a utility function to create a connection pool between the Node.js server and the PostgreSQL server. This function will also export the Prisma Client to be used in the RPC controllers.

Create a server/utils/prisma.ts file and add the following code:

server/utils/prisma.ts


import { PrismaClient } from '@prisma/client';

declare global {
  var prisma: PrismaClient | undefined;
}

export const prisma = global.prisma || new PrismaClient();

if (process.env.NODE_ENV !== 'production') {
  global.prisma = prisma;
}

async function connectDB() {
  try {
    await prisma.$connect();
    console.log('? Database connected successfully');
  } catch (error) {
    console.log(error);
    process.exit(1);
  } finally {
    await prisma.$disconnect();
  }
}

export default connectDB;

In every API architecture, it’s always recommended to create services to access and mutate the database instead of doing that directly in the controllers.

To do this, create a server/services/post.service.ts file and add the following service definitions:

server/services/post.service.ts


import { Prisma, Post } from '@prisma/client';
import { prisma } from '../utils/prisma';

export const createPost = async (input: Prisma.PostCreateInput) => {
  return (await prisma.post.create({
    data: input,
  })) as Post;
};

export const findPost = async (
  where: Partial<Prisma.PostWhereInput>,
  select?: Prisma.PostSelect
) => {
  return (await prisma.post.findFirst({
    where,
    select,
  })) as Post;
};

export const findUniquePost = async (
  where: Prisma.PostWhereUniqueInput,
  select?: Prisma.PostSelect
) => {
  return (await prisma.post.findUnique({
    where,
    select,
  })) as Post;
};

export const findAllPosts = async (
  {page, limit, select}:
 { page: number,
  limit: number,
  select?: Prisma.PostSelect},
) => {
  const take = limit || 10;
  const skip = (page - 1 ) * limit
  return (await prisma.post.findMany({
    select,
    skip,
    take,
  })) as Post[];
};


export const updatePost = async (
  where: Partial<Prisma.PostWhereUniqueInput>,
  data: Prisma.PostUpdateInput,
  select?: Prisma.PostSelect
) => {
  return (await prisma.post.update({ where, data, select })) as Post;
};

export const deletePost = async (where: Prisma.PostWhereUniqueInput)=> {
  return await prisma.post.delete({where})
}

Step 5: Create the RPC Handlers

In this section, we will create five RPC handlers that will be evoked to:

createPostHandler – This RPC handler will be evoked to insert a new record.
UpdatePostHandler – This RPC handler will be evoked to update an existing record.
findPostHandler – This RPC handler will be evoked to retrieve a single record.
findAllPostsHandler – This RPC handler will be evoked to retrieve a paginated list of records.
deletePostHandler – This RPC handler will be evoked to delete a record.

But before we start creating the RPC handlers, create a server/controllers/post.controller.ts file and add the following imports.