Jump to content

The ultimate community for Ruby on Rails developers.


What do you prefer? Fatty or Skinny Model?

  • This topic is locked This topic is locked
1 reply to this topic

#1 Rowel



  • Members
  • 109 posts

Posted 05 September 2013 - 07:50 PM

This is not SPAM.

Yeah, the title kinda sounds spammy :)


I came across an article of recommending moving as much stuff from the Controller to the Model. I guess the Fat Controller/Skinny Model vs. the Skinny Controller/Fat Model.  


Any tips on what generally should be moved from the Controller to the Model ?  

Or is having a big controller okay?  


And can you give examples?  


I tend to see Controllers as the well, controller... and the Models as just the database (with an SQL database linked behind the scenes).  The Controller just dumps it's data to the Model after massaging it.  So how do you move controller duties and code to the Model?


What's your view on this? Interested to hear from the Rails veterans most especially. 

#2 Jamie



  • Moderators
  • 142 posts
  • LocationNewcastle, UK

Posted 05 September 2013 - 08:28 PM

Continue the discussion in a thread I started a while back..






  • jack likes this

Rails developer based in Newcastle, UK.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users