Home/ Questions/Q 372801
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T14:14:45+00:00

I am in the process is designing a website in ASP.NET MVC and am

  • 0

I am in the process is designing a website in ASP.NET MVC and am perhaps a little confused as to the exact nature of a repository.

Following the NerdDinner example, my site should have one repository which serves up the entities as I need them. However, I have also heard that you should have different repositorys that deal with specific sets of related entities….?

In the case of my site, there will be a number of entities (around 15 tables) yet the majority are all related. Is it ok / advisable to have one repository that contains all the methods that I’ll need for pulling / updating / deleting etc or should I split them down?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I create a repository for each data object.

    For example, a simple library database could contain the following repositories:

    • AuthorRepository
    • BookRepository
    • PublisherRepository
    • 0