Understanding Prisma Pulse
I'm trying to figure out if there is any use case for me for Prisma Pulse - when I hear real time subscriptions, I think firebase - where I'm building a front-end app that uses prisma directly to query / load data from the database. I have an app with an api and several front ends - the API is a nest server, and we use apollo for subscriptions right now. In this setup, there would be no real benefit to pulse as we already have real time data subscriptions - am I wrong?
2 Replies
Db change events are great for things like populating computed fields, audit logging, and EDS
I think you’re right, you don’t seem to have a need at the moment
Hi @justinhandley 👋 What is powering the resolver for you Apollo subscriptions? That's a perfect fit for Prisma Pulse in many apps. The Pulse APIs return objects that implement
AsyncIterator, which is exactly what Apollo expects as a subscription resolver. You can use Pulse to subscribe to database changes combined with Apollo to deliver those changes to the frontend.