Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    What's the benefit of these conversions? decoupling the persistence data model from the data model (representation) offered to the consumers. The benefits of decoupling has been widely discussed in S.E. However, the aim beneath DTOs is to gather in a single response as many info as deemed necessary for clients to save calls to the server. What makes the communication client-server smoother. Commented Jun 28, 2018 at 13:02
  • 2
    Possible duplicate of Is it good practice to use entity objects as data transfer objects? Commented Jan 15, 2019 at 11:05
  • Your example is nice. When you are the client (views...) is painful to change, but the biggest problem is when the system already have integrations of 3th party, that is impossible to change (contract, fees...). If your system will have third-party integration, ever use DTO. Commented Jan 30, 2019 at 17:09