As the maintainer of https://pothos-graphql.dev/ , I can offer my perspective. If what you are after is exposing your db as a graphql api, there are better options like https://www.graphile.org/postgraphile/ or https://www.edgedb.com/showcase/graphql I think for building an intentional API with a Prisma based db, the Pothos Prisma plugin does a pretty good job: https://pothos-graphql.dev/docs/plugins/prisma If you want something a little more generated, there is the prisma-utils plugin, which serves as a base for different code generators, or can be used on its own. I am personally unconvinced of the utility of an API generated off of your db schema without a very well thought out auth story, which I haven't really seen in most of the generated graphql APIs. There are a number of tools to generate Pothos schemas based off a Prisma schema, but if you are going that route, Id go all the way and use something like the tools I mentioned above. I think for most apps, intentionally building a graph using the Prisma plugin would result in a much better API, and will be easier to maintain and evolve as your use cases and data sources change over time. More on reddit.com

I have a project using tsyringe and a RESTFul API. Now i should to add a GraphQL API using the type-graphql but in our documentation no have some example using it. Is possiblem to use tsyringe to m... More on stackoverflow.com

Thanks for the comparison! Like you, i've switch from TypeORM to Prisma 2. I still have not found the perfect solution, but one, that is pretty enjoyable to work with. My tool of choice is graphql-code-generator . In the codegen.yml you can map the graphql-types to models of your choice (classes, types, interfaces or objects returned from prisma), specify the context for resolvers, etc... I define the graphql Schema (it can load a variety of different formats - *.graphql, urls, *.{ts,js}-files and some more). Then i run the 'graphql-codegen' command to generate type safe resolvers. After i generated the types, i can create Objects or Classes that implement the Resolvers to have type safety. What i like about this approach is the strict separation between db-schema and graphql-schema but not losing the type safety because my types are generated from the graphql-schema files. If the schema changes, i just have to edit the schema-definitions, regenerate the types and fix the resolvers. Another nice feature is the option, use generate type safte clients for the frontend. More on reddit.com

A place for interesting and informative GraphQL content and discussions · Looking for advice on best practices with this stack More on reddit.com