Timeline for Repository interfaces returning DTO in clean architecture used by query handlers
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25 at 20:22 | comment | added | Filip Milovanović | "This means that repository interfaces for query handlers cannot be in the Domain layer" - no, I would rather say this means that DTO-returning services aren't repositories as DDD envisioned them. A repo is supposed to provide you with initial access to a domain object or an aggregate you cannot otherwise navigate to, and the querying/mapping happens under the hood. There's some friction here when you're using an ORM, so in practice, teams often end up with database-centric code, and treat ORM entities as (anemic) domain objects. Not an unreasonable thing to do, but has its drawbacks. | |
| Feb 25 at 20:16 | answer | added | Ewan | timeline score: 2 | |
| Feb 25 at 20:06 | answer | added | candied_orange | timeline score: 1 | |
| Feb 25 at 18:08 | answer | added | Greg Burghardt | timeline score: 3 | |
| Feb 25 at 18:02 | history | asked | MrChudz | CC BY-SA 4.0 |