Hi, just read the blog post about the prisma clien...
# orm-help
m
Hi, just read the blog post about the prisma client beta release and it looks very interesting. I was wondering: What does this mean for prisma bindings and schema delegation? Is the the prisma client supposed to replace bindings and delegation in the future? Or create an easy alternative to them? If I create a gateway server for multiple prisma microservices, should I import the clients generated in the microservices into the gateway instead of creating service bindings/delegating to them?
👍 1
j
m
Thx
d
Generally, when you want to use schema delegation use
prisma-bindings
and when you are writing a CLI tool or rest backend use Prisma client. Although, there is a bit of overlap between the two.. we aim to resolve the confusion by removing
$delegate
API from the client. You will still be able to perform complicated tasks with client using GraphQL query or raw DB queries directly.
m
Hi @divyendu, thanks for your response. So I shouldnt migrate to the client at all?
d
If you are using schema delegation then maybe not at the moment.
j
Interesting. I find it confusing that most of the docs now use prisma.client, and mention briefly prisma.$delegate, but almost never prisma-bindings. Moreover I find it hard to understand how to do what the primary goal of prisma was to me: create a graphql api on top of a db.
n
Hey @Jidé, I know this is coming very late but we've just created a comprehensive post in the forum that hopefully sheds a bit more light on the distinction of Prisma client and Prisma bindings. You can find it here: https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394/17
j
Awesome @nikolasburk, this really helps understanding the why of prisma-client better. Keep up the good work !
m
@nikolasburk Thanks! 🙌 Clears up a lot of thoughts on the subject. Is there a prisma roadmap? It would be good to have new major features like the client in eyesight before they hit you like a bus 😛
👍 1