Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I do find it confusing I always thought Prisma was GraphQL related.

This is a common misconception that stems from our history as a company and being early contributors to the GraphQL ecosystem. With the move to Prisma 2 however, there is no native GraphQL layer in Prisma any more. I've talked about this extensively in a recent livestream on Youtube [1] if you want to learn more :) There's also this article "How Prisma and GraphQL fit together" [2] that explains the historic dimensions of this if you're interested.

> It's unclear what's the pros are of Prisma compared to TypeORM.

I guess you could argue that one benefit is the superior type-safety Prisma provides [3]. Other folks have also called out that they prefer way how data is modeled with Prisma (via the Prisma schema), the migration system as well as the active maintenance, regular releases, the active community, the support and thorough documentation of Prisma. Ultimately it'll come down to your personal preference though which one is the more appropriate for your project :)

[1] https://www.youtube.com/watch?v=hMWMPpy4ta4&list=PLz8Iz-Fnk_...

[2] https://www.prisma.io/blog/prisma-and-graphql-mfl5y2r7t49c

[3] https://www.prisma.io/docs/concepts/more/comparisons/prisma-...



I skipped Prisma when I discovered that you were supposed to toss your schema in a single file. There's some ways to get around this but amazed that this is the official way




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: