title: Interface between Controller and Service Layer
body: <p>I am a newbie to .Net MVC and my question today is regarding the MVC pattern.</p>
  
  <p>In our application we have a Service Layer which talks with the DB.</p>
  
  <p>The Controller is Currently talking with the Service layer to get the values from the DB.</p>
  
  <p>Our new Manager requires this service layer interaction from the Models and not from the Controller. </p>
  
  <p>He does say that this architecture is to achieve a thin Controller. We are now starting to port the service layer interaction from controller to models.</p>
  
  <p>And here comes my question. Apart from having a thin Controller, is there any other benefits from enforcing this pattern.</p>
  
  <p>I would like to know the advantages and disadvantages of both pattern. </p>
  
  <p>Some links would also be helpful</p>