Timeline for How to avoid pollution of logic with lazy-loaded async properties
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 3, 2019 at 6:14 | comment | added | user1496062 | You can have multiple fetches / run logic it does require smaller more clearly defined units of work so pick your poison. Also can use an aggregate which gets all info and cache it or it manages the fetchs and separates the logic . DDD is a pretty big topic to discuss here and it has its own . For me async / data access in the domain/logic is a red flag which leads to many issues. | |
| Sep 1, 2019 at 7:59 | comment | added | Doc Brown |
Doesn't that lead to a situation where "fetchData" exactly needs to know beforehand which properties of the involved objects have to be loaded for DoLogic, and which are not required? The lazy loading strategy determines this almost automatically, without having that part of the business logic twice.
|
|
| Sep 1, 2019 at 4:50 | review | First posts | |||
| Sep 4, 2019 at 14:25 | |||||
| Sep 1, 2019 at 4:48 | history | answered | user1496062 | CC BY-SA 4.0 |