Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why does the Member Aggregate in the Meetings module need the login information? #310

Open
bonjonrumi opened this issue Feb 22, 2024 · 2 comments

Comments

@bonjonrumi
Copy link

bonjonrumi commented Feb 22, 2024

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.?

@bonjonrumi bonjonrumi changed the title M Why does the Member Aggregate in the Meetings module need the login information? Feb 22, 2024
@Elie-A-98
Copy link

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.

Reference:
https://learn.microsoft.com/en-us/azure/architecture/microservices/model/domain-analysis

image

@bonjonrumi
Copy link
Author

Yes but the data is not used in the meetings module. That module is not doing any kind of authentication or uses the login info in any form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants