Very nice article! I’ve been meaning to play around with both NestJS and Prisma for a while. If I can make a suggestion for a follow up article, would be for pointer-based pagination and caching. Thanks for sharing. More on reddit.com

MikroORM More on reddit.com

As you know the Prisma client generates an interface representing your model (with all the properties). You can use this interface most of the time, but unfortunately not everywhere. Sometimes it's useful and necessary to have a class instead of an interface. For example with Nest's Swagger module, the type property is expecting a value that is available at runtime (it can be a class but not an interface). Another example is the @Exclude decorator that is quite powerful. If you don't use all that feel free to completely remove the class entity and use the Prisma interface instead. More on reddit.com

Hey 👋, Tasin from Prisma here. Answer to your questions Sure many generated types can be used, but a manual DTO creation can't be avoided completely right? You're correct. In general, Prisma defines data types for your data layer. For DTOs in NestJS, you're typically defining the types for your application layer. There might be a strong overlap between the two, but they might not necessarily be a one-to-one mapping. I would personally suggest defining the DTOs manually. How are you managing this in your project: Any tricks on how I can avoid to now create all the DTOs manually for sending data back to the backend? Note that there are some libraries like this one that can help generate DTOs for you. Personally I just write them manually but feel free to use libraries like this. Usually they thought about everything in the docs, has this been forgotten as it's quite common to exclude fields or am I missing something? This is not currently supported by Prisma. There's a github feature request for this. Note that there are some workarounds in the prisma docs . How to elegantly omit a field like a password from your NestJS API For your use case, I would suggest omitting the field using the NestJS Class serialization interceptor instead of removing it at the service level. Here's a quick example of the remove password from the User object case. First, define a UserEntity and annotate the password field with Exclude() so the field is removed during serialization. import { Exclude } from 'class-transformer'; export class UserEntity { // If you have a Prisma `User` type with the same fields, this entity can `implement` the `User` type from '@prisma/client' if you want to reuse Prisma-generated types. id: string; firstName: string; lastName: string; @Exclude() // will remove this field during serialization password: string; constructor(partial: Partial) { Object.assign(this, partial); } } Let's say you have a UserService with a findAll and findOne method: @Injectable() export class UsersService { constructor(private prismaService: PrismaService) {} // These functions return the Prisma User types, with the password included. findOne(id: string): Promise { return this.prismaService.user.findUnique({ where: { id } }); } async findAll(): Promise { return this.prismaService.user.findMany({}); } } Inside the controller, you can define the corresponding route handlers like this: @Controller('users') export class UsersController { @Get(':id') async findOne(@Param('id') id: string) { return new UserEntity(await this.usersService.findOne(id)); } @Get() async findAll() { const users = await this.usersService.findAll(); return users.map((user) => new UserEntity(user)); } } You can globally bind the ClassSerializationInterceptor by adding this line to your main.ts async function bootstrap() { const app = await NestFactory.create(AppModule); app.useGlobalInterceptors(new ClassSerializerInterceptor(app.get(Reflector))); await app.listen(3000); } bootstrap(); Hope this helps! By the way, I'm currently writing a tutorial series about using NestJS and Prisma in the Prisma Blog . The first article shows how to create a basic CRUD REST API. We hope to cover a lot of topics (just like the use case you are talking about in this post) and show best practices in the upcoming articles. I would def suggest checking it out! More on reddit.com