IDbContext and repository pattern #620
Unanswered
BartoGabriel
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Repository interface is part of domain model in ddd and clean architecture |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First, thanks for this repository. It is of great help.
I have some questions regarding the IDbContext and repository pattern.
The Project uses IDbContext and it feels very comfortable to work directly with the EfCore abstraction. It is very useful for the vast majority of use cases.
But in some cases, I have quite advanced and specific SQL queries. I think those deserve to have an application layer abstraction.
Which leaves me with a few questions:
This doubt arises, because in most cases the IDbContext is enough for me.
On the other hand, something I like about the repository pattern is having the aggregate entities identified, and that they only access the parent and not the children. Which brings up the third question:
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions