Model–view–controller (MVC) is a software architecture pattern which separates the representation of information from the user's interaction with it. The model consists of application data, business rules, logic, and functions. A view can be any output representation of data, such as a chart or a diagram. Multiple views of the same data are possible, such as a bar chart for management and a tabular view for accountants. The controller mediates input, converting it to commands for the model or view.
MVC Design Rules
I am using RGB to present MVC. Different colors have different meaning or design rules for the different element.
- Blue stands for intelligence, which means the controller should be very smart.
- Red stands for critical, which means Model is the kernel of the system.
- Green stands for friendly, which means View should be friendly to users.
ASP.NET and MVC
First of all, we know there is a term ‘Web Form’ we should mention and it looks like:
Web Forms are using the PostBack to handle the data directly and not central controller.
So, we introduce the MVC to handle all the interaction with users.
From the above graph, we can see the View has been showed to the customer. There is something special for the Website system. At a specific moment, there are two copies of views: one is at the server side and the other is located at the client side.
Yes, maybe we can do something at the client side, as we have the View. Let’s make some magic with AJAX. We are using the AJAX to build a controller to bridge the data at the server side and View we have.
With this role, the server has changed it from a webpage server to Web Service and the difference is that it provides the data not the page now.
Although the controller and content of view are in the same file, they can be identified with different content. The controller is enclosed by
<script></script> and the content is by the html definition, like
One thing I would like to mention is that there is the other way to isolate the View from the Model, which is MVVM (knockoutJS is a typical one). So, what the difference is Controller knows everything of the View, while ViewModel knows nothing about the View and it just provides the objects and methods to wait for the View to bind.
Nevertheless, MVVM is a really good idea for the markup language style View, like .xaml for the WPF.
WPF and MVVM
Based on previous analysis, we can easily get the architecture of WPF with Web Service which is as follows:
And a pure local one looks like below:
At the very beginning, in ASP.NET, we used
DataSet to keep the data we retrieved from the SQL Server by Query and then we encapsulated the
DataSet into an object.
To simply this, we invent the ORM (Object Relational Mapping) and we have Entity Framework which maps the data in database to the object directly.
Furthermore, we can design the Model first, or Database first, even the code first with the Entity Framework.
MVC and Hybrid Application
Controller Evolution – Soap Style vs. REST Style
- Soap Style –
Request is one whole word and it is an action
- REST Style –
DELETE have the different real meaning.
Request has changed to a resource.
iOS and MVC
iOS is a very typical MVC implementation which looks like below. In iOS development, we should make sure Model and View are 100 percent isolated.
Android and MVC
There is not a clear definition of activity, I would like to treat it as a big controller and it contains a number of controllers, here are adapters when it comes to the data. One typical adapter is the cursor adapter when we load the data from a db for a listview.
In brief, MVC is a cutting-edge term and it links the ASP.NET, iOS, Android and Hybrid development together, which makes me easily shift from one developer role to the other. All in all, I hope this paper can help you.
If you have any questions, feel free to contact me by email at email@example.com.