---
title: "Comment by Natã Estanislau Bastos on \"Understanding Data Transfer Objects (DTOs) and Validators in NestJS.\" | Hashnode"
description: "I don&#39;t think you should use the dto pattern in 2023. It adds more boilerplate to your application. You can usually get away with not using it, just using t"
url: "https://hashnode.com/posts/understanding-data-transfer-objects-dtos-and-validators-in-nestjs/6407813b498910cbf9f60aa5/comment/6407ec046c8cbdd4116b84d0"
---

[Discussion](https://hashnode.com/posts/understanding-data-transfer-objects-dtos-and-validators-in-nestjs/6407813b498910cbf9f60aa5)

Comment [Understanding Data Transfer Objects (DTOs) and Validators in NestJS.](https://hashnode.com/posts/understanding-data-transfer-objects-dtos-and-validators-in-nestjs/6407813b498910cbf9f60aa5)

[Natã Estanislau Bastos](https://hashnode.com/@nataneb32)

[Mar 8, 2023](https://hashnode.com/posts/understanding-data-transfer-objects-dtos-and-validators-in-nestjs/6407813b498910cbf9f60aa5/comment/6407ec046c8cbdd4116b84d0)

I don't think you should use the dto pattern in 2023. It adds more boilerplate to your application.

You can usually get away with not using it, just using the entity directly + some parameters.

And when you see a need for it. Just name it CreateUserParams and don't call it CreateUserDTO, DTO has no meaning at all. Use a more semantic name schema.
