title: The effects of adding a Service Layer to a Laravel application
body: <p>I have been developing with Zend Framework for a number of years and am now learning Laravel.</p>
  
  <p>In my previous applications I usually have a Service Layer that is called by controllers.  The Service Layer sits across the top of a Mapper and a Domain Model and is responsible for some application logic, raising events, some input filtering, etc.</p>
  
  <p>Is there any reason why I should not implement a Service Layer in Laravel?  In the examples that I have seen so far, controllers work directly with domain objects (or more accurately, active records).</p>
  
  <p>If my Laravel controllers called my Service Layer, would I lose any of the advantages of Laravel?  (As far as I can see I can still use Route/Model binding).</p>
  
  <p>As a secondary question - what would be the best way to implement my Service Layer?  As a collection of Service Providers, perhaps?</p>