Stream database changes in real-time with Prisma Pulse
Learn how to create event-driven flows on your backend triggered by changes in your Neon Postgres database
Neon's Logical Replication feature enables you to subscribe to changes in your database, supporting things like replication or creating event-driven functionality.
Prisma Pulse is a fully managed, production-ready service that connects to your Neon Postgres database, and allows you to stream changes from your database in real-time, integrated closely with Prisma ORM.
In this guide, you will learn how to set up Prisma Pulse with your Neon database and create your first event stream.
tip
What can you make with database event-driven architecture?
Set up real-time triggers for your Inngest workflows, re-index your TypeSense search whenever data changes, and much more.
Prerequisites
- A Neon account
- A Prisma Data Platform account
- Read the important notices about logical replication in Neon before you begin
Enable logical replication in Neon
important
Enabling logical replication modifies the Postgres wal_level
configuration parameter, changing it from replica
to logical
for all databases in your Neon project. Once the wal_level
setting is changed to logical
, it cannot be reverted. Enabling logical replication also restarts all computes in your Neon project, meaning active connections will be dropped and have to reconnect.
To enable logical replication in Neon:
- Select your project in the Neon Console.
- On the Neon Dashboard, select Project settings.
- Select Beta.
- Click Enable to enable logical replication.
You can verify that logical replication is enabled by running the following query from the Neon SQL Editor:
Connect Prisma Pulse
- If you haven't already done so, create a new account or sign in on the Prisma Data Platform.
- In the Prisma Data Platform Console create a new project by clicking the New project button.
- In the New project configuration, select Pulse as your starting point.
- Copy your database connection string from Neon into the database connection input field on the Platform Console.
- Choose a region that is closest to your Neon database.
- Click Create project.
- We recommend leaving Event persistence switched on (default). This means Prisma Pulse will automatically store events in the case your server goes down, allowing you to resume again with zero data loss.
- Click Enable Pulse.
- After Pulse has been enabled (this may take a moment), generate an API key by clicking Generate API key. Save this for later.
Your first stream
Set up your project
Create a new TypeScript project with Prisma:
If you already have a TypeScript project with Prisma client installed, you can skip this.
From the root of your project, install the Pulse extension
Extend your Prisma Client instance with the Pulse extension
Add the following to extend your existing Prisma Client instance with the Prisma Pulse extension. Don't forget to insert your own API key.
note
For a real production use case, you should consider moving sensitive values like your API key into environment variables.
Create your first Pulse stream
The code below subscribes to a User
model in your Prisma schema. You can use a similar approach to subscribe to any model that exists in your project.
Trigger a database change
You can use Prisma Studio to easily make changes in your database, to trigger events. Open Prisma Studio by running: npx prisma studio
After making a change in Studio, you should see messages appearing in your terminal like this: