Prisma

Good morning! Are people using `nexus` with a microservices approach?
Multiple prisma servers, stitching these, extending them. So far it feels limiting the code first approach when you have to work with an external SDL.

You can use the schema stitching easily with nexus as the output is a graphql schema. There is also a extendType method in nexus.

See: <https://github.com/prisma/nexus/issues/70>

looks like you are the guy that opened the issue in the first place :sweat_smile: .

Please wait for <@U689VJXAN>, he will provide you a reply soon in the issue

I am the same guy :slightly_smiling_face: thanks <@UCZMXEP3J>.

It would be good to get an answer, because I can’t really see a real solution to the problem.
You can stitch yes, as you kindly me showed me. But obviously nexus is not aware of the types stitched separately. So I can’t create a query or mutation in nexus and return a type a stitched in.

BTW the other reason I was posting was also gather other people experiences. Because unless I am missing something, it is quite limiting in certain scenarios.

Nexus is fairly new so I think you are one of the very few people that are using it for this use case

:slightly_smiling_face: I understand that, but the scenario I am on, it is not so strange. That is why I am trying to get a conversation going, see what and how could be improved. Otherwise if there is no conversation, I will just have to not use nexus and go back to SDL first.