4

I have an ASP.NET MVC 2 application with some complex business rules and I'm trying to decide where to put specific logic.

The logic happens when creating records, based on certain fields of that record other records need to be created.

I'm currently using the repository pattern with an ORM and the easiest place to put this logic would be in my repository class but I feel like this is a pretty feeble location to have important rules, I would put it directly in my partial model classes that have my validation and metadata but I then have to call methods within my controller or repository and that may be extending too much knowledge about implementation to those layers.

What are your best practice tips for me?

Thanks!

Jimmy
  • 9,686
  • 14
  • 59
  • 78

1 Answers1

5

You could have a service layer between the controller and the repositories. The repository performs simple CRUD operations with your model. A service method could make use of multiple simple repository calls to compose a business operation. This business operation will be exposed to the controller.

Darin Dimitrov
  • 1,023,142
  • 271
  • 3,287
  • 2,928
  • 1
    When you say service layer, is it implemented as an actual service such as WCF/data services/etc., or is it simply another layer of code/classes between the controllers and repositories? If so, would you typically have one service class for each entity in your model? Do you know of any good examples using this pattern? I have seen some examples using the repository pattern with MVC, but not with a service layer(or maybe it was there and I didn't notice). – AaronLS Aug 11 '11 at 21:54