title: Fat ASP.NET MVC Controllers
body: <p>I have been reading about "Fat Controllers" but most of the articles out there focus on pulling the service/repository layer logic out of the controller. However, I have run into a different situation and am wondering if anyone has any ideas for improvement. </p>
  
  <p>I have a controller with <strong>too many actions</strong> and am wondering how I can break this down into many controllers with fewer actions. All these actions are responsible for inserting/updating/removing objects that all belong to the same aggregate. So I'm not quiet keen in having a seperate controller for each class that belongs to this aggregate... </p>
  
  <p>To give you more details, this controller is used in a tabbed page. Each tab represents a portion of the data for editing and all the domain model objects used here belong to the same aggregate.</p>
  
  <p>Any advice?</p>
  
  <p>Cheers,
  Mosh</p>