You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering why it needs to have this information since it is nowhere used? Isn't it enough to have it in the Users Module whose responsibility it is to have this information and do things like authenticating etc.?
The text was updated successfully, but these errors were encountered:
bonjonrumi
changed the title
M
Why does the Member Aggregate in the Meetings module need the login information?
Feb 22, 2024
In domain analysis, multiple domains can define their own model for the same real-world entity. This is to better achieve encapsulation and separation of concern. So the UserAccess module has a User model which contains the things releveant within the UserAccess bounded context, and some other modul might also define a User model which has the properties relevant to it's bounded context.
I am wondering why it needs to have this information since it is nowhere used? Isn't it enough to have it in the Users Module whose responsibility it is to have this information and do things like authenticating etc.?
The text was updated successfully, but these errors were encountered: