Contents
Can DTO be an interface?
By using interfaces instead of classes when transferring data between our application layers, we can achieve immutability by only defining the getters in the interface.
Where should DTO be?
Depending on their form, a good place for them is either the Application Layer or the Presentation Layer. If the DTOs are only for presentation purposes, then the Presentation Layer is a good choice. If they are part of an API, be it for input or output, that is an Application Layer concern.
Which is layer DTO should be in Domain Driven Design?
DTO is an output of that layer, it make sense if you define it there. Don’t put your DTO in the Domain Layer. The Domain Layer does not care about mapping things to serve external layers (the domain does not know there is a world outside of its own) Presentation Layer (closes to consumers)
Can a DTO be created from a domain object?
The domain object contains no reference to the DTO. An outside entity (a “mapper” or “assembler”) is called to create a DTO from a Domain Object. Normally there is an ORM on the domain object side. The downside of this is that the “mapper” tends to get extremely complex for any real situation and can be very fragile.
When to use DTOs in the application layer?
If the DTOs are only for presentation purposes, then the Presentation Layer is a good choice. If they are part of an API, be it for input or output, that is an Application Layer concern. The Application Layer is what connects your domain model to the outside world.
Which is the correct way to implement DTO Using DDD principles?
The DTO implementation seems part of the Domain, but it means that when I create a collection of DTOs in the Service Layer and pass it to a Presentation Layer, I have to reference Domain Layer in Presentation Layer, which seems wrong. What is the correct way to implement DTO using DDD principles?