-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Prisma Client Node-API Support #4911
Copy link
Copy link
Closed
prisma/prisma-engines
#1544Labels
tech/enginesIssue for tech Engines.Issue for tech Engines.tech/engines/query engineIssue in the Query EngineIssue in the Query Enginetech/typescriptIssue for tech TypeScript.Issue for tech TypeScript.topic: node-apiformerly `nApi`formerly `nApi`
Milestone
Metadata
Metadata
Assignees
Labels
tech/enginesIssue for tech Engines.Issue for tech Engines.tech/engines/query engineIssue in the Query EngineIssue in the Query Enginetech/typescriptIssue for tech TypeScript.Issue for tech TypeScript.topic: node-apiformerly `nApi`formerly `nApi`
Currently the Prisma Client communicates with the Query Engine over HTTP or Unix Domain Sockets. After some experimentation we realized we can cut this overhead down significantly with Node-API.
Node-API binds the Query Engine into the Prisma Client directly, so calling into the Query Engine is no different than calling a Node.js function.
@pimeys has been shown in https://github.com/pimeys/napi-test it's possible to connect from Node.js to the query engine via the Node-API.