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*

4
  • 1
    A "DTO" is just a "Data Transfer Object," nothing more. Commented Aug 27, 2018 at 21:16
  • These two terms are not comparable, one cannot put them in a "vs" relation. As an example, a read model can use (local) DTOs to represent the returned entities. Commented Aug 28, 2018 at 4:35
  • @Constantin Galbenu Aren't read models there to cover specific use cases? Why would I then need a DTO to adjust the returned data to my use case? Commented Aug 28, 2018 at 9:20
  • 1
    A DTO is just a plain object that carry some data. A read-model answers to some query and returns something, i.e. a list of DTO Commented Aug 28, 2018 at 9:33