Comments on: Fat Models, Skinny Controllers

By: MVC, CakePHP et Rock’n’Roll !

MVC, CakePHP et Rock’n’Roll ! — Tue, 01 Sep 2009 08:14:02 +0000

[...] dans le modèle, dans un but à la fois “DRY” et afin de suivre le précèpte “Fat Models, Skinny Controllers“. Dans le cas présent, nous partirons du principe que le formatage des données n’a [...]

By: Sandor

Sandor — Fri, 14 Aug 2009 09:42:55 +0000

+1 for @Rogerio
The only question remains is where to put this classes in case of cakephp?

By: Rogerio Senna

Rogerio Senna — Sun, 28 Jun 2009 23:11:12 +0000

Just my two cents:

First of all, “fat models” are the way to go, IMHO.

But “Model” is a tier, from the MVC architecture perspective. It is not a single class, not even a single pattern.

Why I say that? When a cakephp programmer speaks about a “model”, he is normally talking about a specific implementation of the the “Active Record” design pattern (made by the cakephp team through the AppModel class), used for data persistence and ORM.

But a model is much more than that. It is also the right place for business logic, validation etc.

The cakephp team have incorporated much of these features inside the AppModel class, witch is really cool, but is not always enough. Sometimes, in complex systems, it would be better to have other classes (like façades, bridges, whatever) to manipulate and consolidate data.

You can call this classes BLLs, or managers, or whatever you like. But they STILL belong to the “model” tier, even if they are not subclasses of the AppModel class. And so, even doing that, you are still using a MVC architecture (in fact, probably a much more improved one).

Sorry for the whining (and for the bad english), just trying to make things a little bit more clear.

By: laneolson.ca | Beginning CakePHP: The MVC Mindset

laneolson.ca | Beginning CakePHP: The MVC Mindset — Sat, 23 May 2009 02:44:40 +0000

[...] to a minimum and instead put the bulk of the code for manipulating the data into the model (see Fat Models, Skinny Controllers by Chris [...]

By: Fat Model and Skinny Controller | Prajwal Tuladhar's Blog

Fat Model and Skinny Controller | Prajwal Tuladhar's Blog — Wed, 31 Dec 2008 02:59:30 +0000

[...] days ago, I read a post (the post is a bit old) about the the design concept of fat model, skinny controller. After going [...]

By: Beginning CakePHP: The MVC Mindset « Lane Olson’s Blog

Beginning CakePHP: The MVC Mindset « Lane Olson’s Blog — Mon, 08 Dec 2008 20:36:05 +0000

[...] to a minimum and instead put the bulk of the code for manipulating the data into the model (see Fat Models, Skinny Controllers by Chris [...]

By: Kiran Aghor

Kiran Aghor — Thu, 04 Sep 2008 14:29:49 +0000

I read somewhere about fat-model and skinny controllers. But was wondering how to code that way. This post shows it clearly. Thanks a lot.

By: deltawing

deltawing — Fri, 27 Jun 2008 22:32:08 +0000

I think the better way to say it would be , “models should be fat in relation to controllers”. That is, keep everything down to the minimum possible.

By: Chris Hartjes

Chris Hartjes — Tue, 18 Mar 2008 13:22:36 +0000

@James

Well, it’s not really a CakePHP-specific thing. It’s more a application architecture issue with any framework that tries to follow the Model-View-Controller pattern.

By: james

james — Tue, 18 Mar 2008 02:50:59 +0000

Thanks for the article … I only wish I knew about this earlier. The CakePHP manual doesn’t mention this (I don’t think).