Prisma

Hi. I am considering a stack for a new application. Asking for opinions on Prisma+Apollo+NestJS vs Prisma+Apollo.
NestJS offers ways to maintain the schema, Apollo of course, but Prisma offers it too. I want to use migrations. Would NestJS even be a benefit in this case? If I use Prisma to maintain the schema, will that generate a GraphQL schema that NestLS can use? Thanks for any advice.

I’m assuming you are talking about Prisma 2. In that case, Prisma is just an ORM.

We are using this stack at work. Prisma and GraphQL schemas are completely separate, you would need to create the graphql types for outputs yourself via either method (code-first or schema-first).


In my experience so far building the GraphQL layer with Prisma and their type-graphql implementation is a little bit confusing. You still have to create classes with decorators in code first and the graphql schema in schema first.

<@U02DNSKRGCF> :wave:
You can go for autogenerated crud resolvers like TypeGraphQL does <https://typegraphql.com/docs/prisma.html|here>. So NestJS is not required in this case.