MVC repository pattern design decision

Posted by bradjive on Stack Overflow See other posts from Stack Overflow or by bradjive
Published on 2010-03-15T19:29:33Z Indexed on 2010/03/15 19:39 UTC
Read the original article Hit count: 989

I have an asp .net MVC application and recently started implementing the repository pattern with a service validation layer, much like this.

I've been creating one repository/service for each model that I create. Is this overkill? Instead, should I create one repository/service for each logical business area that provides CRUD for many different models?

To me, it seems like I'm either cluttering the project tree with many files or cluttering a class with many methods. 6 one way half dozen the other. Can you think of any good arguments either way?

© Stack Overflow or respective owner

Related posts about repository-pattern

Related posts about