title: ASP.NET MVC - Should business logic exist in controllers?
body: <p>Derik Whitaker posted an <a href="http://devlicio.us/blogs/derik_whittaker/archive/2008/10/22/how-is-interacting-with-your-data-repository-in-your-controller-different-or-better-than-doing-it-in-your-code-behind.aspx" rel="noreferrer">article</a> a couple of days ago that hit a point that I've been curious about for some time: <strong>should business logic exist in controllers?</strong></p>
  
  <p>So far all the ASP.NET MVC demos I've seen put repository access and business logic in the controller.  Some even throw validation in there as well.  This results in fairly large, bloated controllers.  Is this really the way to use the MVC framework?  It seems that this is just going to end up with a lot of duplicated code and logic spread out across different controllers.</p>