Thursday, February 28, 2019

Is using the repository pattern best practise?

I'm following a .net core an Angular course on udemy.

​

The application architecture follows the repository pattern. For example theres a user repository that has the logic, which implements an interface. The controller then calls the methods in each function. Is this best practise? Or should I avoid repository and implement all the CRUD functionality in the controller itself.

​

In my previous job, (using Laravel) we were refactoring an application, and my boss told me to strip out the repositories and implement all logic in the controllers?

​

Should I do this?

Is using the repository pattern best practise? Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team