It’s a bit tough to give you the “right” answers, since some of them deal with the specifics of the framework (regardless of the ones you are working with). At least in terms of CakePHP: Yes Anything that deals with data or data manipulation should be in a model. In terms of CakePHP what about … Read more
Gee, Brian, I wish I had seen your question sooner. Since it’s pretty much my “invention” (for better or worse), I might be able to help. Inserted: The shortest possible explanation I can make is that if normal execution is like throwing a ball in the air and catching it, then differential execution is like … Read more
The service layer can be interpreted a lot of ways, but it’s usually where you have your core business processing logic, and sits below your MVC architecture, but above your data access architecture. For example, you layer of a complete system may look like this: View Layer: Your MVC framework & code of choice Service … Read more
Domain and model objects are essentially the same, and may contain business logic. Depending on implementation, domain and DTO objects may be equivalent if you remove business logic from the model into a service class. Often a key variant of the DTO is the View Model, which is used purely to transfer data between the … Read more
It might not be the best idea to look at Rails as a staple of MVC design pattern. Said framework was made with some inherent shortcomings (I kinda elaborated on it in a different post) and the community only just now has begun addressing the fallout. You could look at DataMapper2 development as the first … Read more
Short answer Qt’s MVC only applies to one data structure. When talking about an MVC application you should not think about QAbstractItemModel or QListView. If you want an MVC architecture for your whole program, Qt hasn’t such a “huge” model/view framework. But for each list / tree of data in your program you can use … Read more
MVC is more of an architectural pattern, but not for complete application. MVC mostly relates to the UI / interaction layer of an application. You’re still going to need business logic layer, maybe some service layer and data access layer. That is, if you’re into n-tier approach.
N-tier architecture usually has each layer separated by the network. I.E. the presentation layer is on some web servers, then that talks to backend app servers over the network for business logic, then that talks to a database server, again over the network, and maybe the app server also calls out to some remote services … Read more
There are two major differences between Observer/Observable and Publisher/Subscriber patterns: Observer/Observable pattern is mostly implemented in a synchronous way, i.e. the observable calls the appropriate method of all its observers when some event occurs. The Publisher/Subscriber pattern is mostly implemented in an asynchronous way (using message queue). In the Observer/Observable pattern, the observers are aware … Read more
A Data Transfer Object is an object that is used to encapsulate data, and send it from one subsystem of an application to another. DTOs are most commonly used by the Services layer in an N-Tier application to transfer data between itself and the UI layer. The main benefit here is that it reduces the … Read more