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

Determining which modules own whicn entities #338

Open
josealbertocoronado opened this issue Sep 27, 2024 · 0 comments
Open

Determining which modules own whicn entities #338

josealbertocoronado opened this issue Sep 27, 2024 · 0 comments

Comments

@josealbertocoronado
Copy link

josealbertocoronado commented Sep 27, 2024

Hi, thanks for this repo, really useful.
I wanted to ask about something that has caught my attention:

MeetingGroupProposal entity exists both in ApplicationContext and MeetingContext and I'm wondering whether that's correct from a DDD perspective?
I mean, shouldn't each entity be owned by one (and only one) module? Is it ok to have more than one module accessing to the same entity directly? With that approach, nothing prevents us from starting use the same entity in more modules, ending up with all modules been able to access all entities? also, how would that work if we wanted to separate modules in different databases?

Let's say this was a microservices architecture rather than a modular monolith: in that case only one of the microservices would have access to the entity, the other one should get that data differently (maybe by caching it via integration events). Is it not he same idea here?

Thanks in advance.
Regards,

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

1 participant