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
Hello,
Sorry for too many questions. I've been studying this architecture lately and came up across this question?
Is it better to create a single Create() method in repository layer and have many usecase methods that creates the entity or having different method for Create() operation in repository layer for so every usecase that requires a Create() method could have it's own dedicated method for creating the entity?
Appreciate your feedback. Thank you and have a nice day ahead.
The text was updated successfully, but these errors were encountered:
Agree with @frederikhors
The repository is meant to be re-used by the usecase/service layer as the orchestrator. The service layer knows which repos they want, and orchestrates the repos as needed.
Hello,
Sorry for too many questions. I've been studying this architecture lately and came up across this question?
Is it better to create a single Create() method in repository layer and have many usecase methods that creates the entity or having different method for Create() operation in repository layer for so every usecase that requires a Create() method could have it's own dedicated method for creating the entity?
Appreciate your feedback. Thank you and have a nice day ahead.
The text was updated successfully, but these errors were encountered: