I honestly can't think of any job I'd be happy leaving in the hands of a controller beyond the obvious HTTP routing and view rendering concerns. Even adding a

I honestly can't think of any job I'd be happy leaving in the hands of a controller beyond the obvious HTTP routing and view rendering concerns. Even adding a presenter, as I prefer, serializing your data should be handled by your service layer. I'm not advocating writing an ORM, just some simple data translations from the raw database row data to a persistence-free domain object.