Hi guys, I’m researching the possibility of making prisma engine as a microservice in our cluster. I looked at some of the source codes and find that currently the url of the engine is hardcoded to be

localhost

. I’d like to ask if there is any plan to support the use case I mentioned (point the engine endpoint url from the client and start a standalone engine), further more, I want to ask what’s the plan for NodeEngine since the napi is in preview. Do you guys want to replace the NodeEngine with NapiEngine or keep both?

@Evan Jia 👋 I would suggest adding your thoughts in this request so that we can look into the specific use cases for this 🙂

Hey Evan, thanks for bringing this up 🙂

I’d like to ask if there is any plan to support the use case I mentioned (point the engine endpoint url from the client and start a standalone engine)

Ryan already shared a relevant issue for this use case, I think this one could also be interesting for you: https://github.com/prisma/prisma/issues/100

Do you guys want to replace the NodeEngine with NapiEngine or keep both?

We will definitely keep both approaches but napi is likely going to be the default going forward. (Whether it'll become the default also depends on whether we learn about any downsides of this approach during the Preview phase 🙂 )

Thanks guys, will proceed further on the issues.