What is the use of repository pattern in MVC?

Question

The context uses the unit of work pattern and each DBSet is a repository. Why is Repository pattern useful?

Rajanikant Hawaldar · Answer

Hi Tamal Marick, Repository pattern is an abstraction layer you put on your data access layer. Your data access layer can be anything from pure ADO.NET stored procedures to Entity Framework or an XML file. In large systems, where you have data coming from different sources (database/XML/web service), it is good to have an abstraction layer. The Repository pattern works well in this scenario. I do not believe that Entity Framework is enough abstraction to hide what goes on behind the scenes. I have used the Repository pattern with Entity Framework as my data access layer method and am yet to face a problem. Another advantage of abstracting the DbContext with a Repository is unit-testability. You can have your IRepository interface to which has 2 implementations, one (the real Repository) which uses DbContext to talk to the database and the second, FakeRepository which can return in-memory objects/mocked data. This makes your IRepository unit-testable, thus other parts of code which uses IRepository. public interface IRepository { IEnumerable GetCustomers(); } public EFRepository : IRepository { private YourDbContext db; private EFRepository() { db = new YourDbContext(); } public IEnumerable GetCustomers() { return db.Customers.Select(f=> new CustomerDto { Id=f.Id, Name =f.Name}).ToList(); } } public MockRepository : IRepository { public IEnumerable GetCustomers() { // to do : return a mock list of Customers // Or you may even use a mocking framework like Moq } } Now using DI, you get the implementation public class SomeService { IRepository public class SomeService { IRepository repo; public SomeService(IRepository repo) { this .repo = repo; } public void SomeMethod() { //use this.repo as needed } }

Gajendra Jangid · Answer

The repository pattern is intended to create an abstraction layer between the data access layer and the business logic layer of an application. It is a data access pattern that prompts a more loosely coupled approach to data access. We create the data access logic in a separate class, or set of classes, called a repository with the responsibility of persisting the application's business model. https://www.c-sharpcorner.com/UploadFile/3d39b4/crud-using-the-repository-pattern-in-mvc/ https://www.c-sharpcorner.com/uploadfile/8a67c0/repository-pattern-with-asp-net-mvc-with-entity-framework/

Tamal Marick · Answer

The repository pattern is intended to create an abstraction layer between the data access layer and the business logic layer of an application. It is a data access pattern that prompts a more loosely coupled approach to data access.

Sanwar Ranwa · Answer

Hello Check these Links https://stackoverflow.com/questions/8749153/why-use-repository-pattern-or-please-explain-it-to-me https://docs.microsoft.com/en-us/aspnet/mvc/overview/older-versions/getting-started-with-ef-5-using-mvc-4/implementing-the-repository-and-unit-of-work-patterns-in-an-asp-net-mvc-application