Timeline for DDD, where to use infrastructure services
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 8, 2018 at 8:37 | history | suggested | smac89 | CC BY-SA 4.0 |
Fix grammer and added code ticks
|
| Jun 7, 2018 at 21:57 | review | Suggested edits | |||
| S Jun 8, 2018 at 8:37 | |||||
| Sep 7, 2016 at 16:53 | comment | added | jhyot | Actually, services are an integral part of DDD. See eg. en.wikipedia.org/wiki/Domain-driven_design#Building_blocks | |
| Sep 7, 2016 at 9:04 | comment | added | mfrachet | Thanks for your answer. I got the difference between the playin record and I agree with you concerning statelessness. My concern is on how my project would be manage, concerning dependency injection. For me, after what you've given me, I would have : Application Service <- Hosting service <- Domain service <- Infrastructure service, with Domain service managing my domain objects . (the arrows means the direction of the injection). Have I got it ? | |
| Sep 7, 2016 at 7:37 | history | edited | Ewan | CC BY-SA 3.0 |
added 394 characters in body; deleted 1 character in body
|
| Sep 7, 2016 at 7:31 | history | answered | Ewan | CC BY-SA 3.0 |