Timeline for How to model 1 to many relationships in DDD (Domain Driven Design)
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2022 at 16:14 | comment | added | Christophe | @alaboudi I’d inject the organization and the user into the service. Membership would reference user by ID. Depends on what you call huge, but wouldn’t lazy loading be an option? The last one deserves its own question ;-) | |
| Mar 8, 2022 at 13:28 | comment | added | alaboudi | Yes you pretty much captured it nicely. Members only make sense as part of the org but users exist regardless. I have a few questions though. Would this service be injected into the organization or would the organization be injected into the service? In either case, how would you handle instantiating an organization with a huge list of members? Is it ok to inject a repository outside the app service layer? | |
| Mar 8, 2022 at 10:42 | history | answered | Christophe | CC BY-SA 4.0 |