Timeline for Three layer architecture and using DTOs to transfer data between layers
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 17, 2024 at 19:08 | comment | added | Laiv | Ideally, domain and BL are in the core of the design, so they are common to all upper layers. Upper layers can be coupled to core elements. It's the opposite what's not recommended. | |
| Aug 16, 2024 at 7:33 | comment | added | Pawan Nogariya | @Laiv It is not recommended to have DAL layer only work with entities and other layers, in this case even BLL should not know or have access to the database entities? What I have read as recommendation is to have DLL return DTO and not entity directly and then this DTO can be used as many layers as you want to | |
| Nov 24, 2022 at 10:03 | vote | accept | Alfons Deda | ||
| Nov 24, 2022 at 9:56 | comment | added | Laiv |
To the first question. No, DTOs belong to UI (or outer layers). BBL only works with domain entities and business entities/ports. To the second question: what to update is business logic and how to update/persist/fetch is the repository's logic.
|
|
| Nov 23, 2022 at 20:40 | comment | added | Alfons Deda | Sorry one question, method that not interact with all the entity, for example retrieve or update only some data should be in service layer or directly in repository? | |
| Nov 23, 2022 at 19:34 | comment | added | Alfons Deda | thanks for you response. So, you mean to add DTOs only from BLL to UI and BLL to interact directly with DAL entities? | |
| Nov 23, 2022 at 13:34 | history | edited | Laiv | CC BY-SA 4.0 |
deleted 42 characters in body
|
| Nov 23, 2022 at 13:28 | history | answered | Laiv | CC BY-SA 4.0 |