✅ What is Repository pattern design and how to implement it
Hello guys, I was just learning about how to implement database connection using the EF Core, then I came across something known as
I understood that we uses some kind of abstraction to separate these logic. Like we create a specific class for data access logic, we only want to interact with the database while, for the business logic, this is still a bit confusing; can someone elaborate please.
When we picture the business logic and data access logic, how do we implement that in code please (Are there steps to follow?).
Last thing, is this important? :c ..Can't I just merge everything, both logics?
Repository patternI understood that we uses some kind of abstraction to separate these logic. Like we create a specific class for data access logic, we only want to interact with the database while, for the business logic, this is still a bit confusing; can someone elaborate please.
When we picture the business logic and data access logic, how do we implement that in code please (Are there steps to follow?).
Last thing, is this important? :c ..Can't I just merge everything, both logics?
