MVC 1 & MVC 2 architecture Difference

MVC 1 & MVC 2 architecture Difference

Here we see the MVC 1 & MVC 2 architecture difference:

In MVC 1 & MVC 2 the both architecture have same View

(Presentation part layer) and Controller (Configuration layer) but the difference in Model part.

Let’s we see the difference on figure:

Figure 1: MVC 1 Architecture

Figure 2: MVC 2 Architecture

In the Above Figure 1 & Figure 2 we see that view and the controller part work is same in both architecture but the difference is that the Model part:

In MVC 1 architecture the MVC 1 have the combine the Business logic and Database Access (DBA) and web services.

In MVC 2 architecture the MVC 2 have not combine the Business logic and Database Access (DBA) and web services.

MVC 2 architecture

MVC 2 architecture

MVC 1 architecture we see that MVC 1 provide the full facility to separate the Model, View,Controller.

 The advantage of MVC 1 architecture is that its provide the separate presentation (VIEW), Configure (Controller), Business logic (Model). 

But the main disadvantage of MVC 1 architecture is that the Model part has combine the Database Access, Core Business logic ,and  Web services .so there is lots of problem to maintain the DBA and business logic

For Solving the above MVC 1 problem of Model is Overcome in MVC 2 Architecture which provide the Model part to divide in different to Database Access (DBA), Core Business logic, and Web services.

Let we See the MVC 2 architecture Figure.

• Request send by the user from browser (View layer) is going to controller part from view
• The particular request come from the view part is handle by the controller part and the Controller decide which action (business logic file) is called for the particular request from  the view. 
•  Most Important part in the MVC architecture the model part in which the controller call the particular action file which is provided by the Model part

The most important thing in MVC 2 architecture is that the Model part  are not  combine its all are separate and connect to each other the all database access (DBA), Business logic, web services are in one file of model part.

So this is the advantage of MVC 2 architecture is that its provide the separate presentation (VIEW), Configure (Controller), Business logic (Model). 

MVC 2 architecture is that the Model part has separate  the Database Access, Core Business logic ,and  Web services.so there is need to connect the separate the each other the in model part.

And make the application ease to maintain

MVC 1 Architecture

MVC 1 architecture

In MVC 1 architecture we know the work of the model, view and Control. 

But there are some different in MVC 1 architecture and its update version MVC 2,

Let we know MVC 1 architecture.

First We see the figure of MVC 1 architecture.

From the figure we see that:

•      Request send by the user from browser (View layer) is going to controller part from view.
•   The particular request come from the view part is handle by the controller part and the controller   decide which action (business logic file) is called for the particular request from the view.
•     Most Important part in the MVC architecture the model part in which the controller call the particular action file which is provided by the Model part.

The most important thing in MVC 1 architecture is that the Model part combine the all database access (DBA), Business logic, webservices are in one file of model part.

So this is the advantage of MVC 1 architecture is that its provide the separate presentation (VIEW), Configure (Controller), Business logic (Model). 

But the main disadvantage of MVC 1 architecture is that the Model part has combine the Database Access, Core Business logic ,and  Webservices.so there is lots of problem to maintain the DBA and business logic

Previous                                                                                                                                                                                           Next

The Model-View-Controller Pattern – Overview & Benefit

•         Splits up responsibilities for handling user interactions in an application into three layers:

–        Model, View, Controller

 Model

–         holds application data and business logic

–         is absolutely independent from the UIs

  View

–        presentation of parts of the Model to the user

–        independent from the internal implementation of the Model

–        there can be different Views presenting the same Model data

Controller

–        “bridge” between Model and View

–        controls the flow of the application

•         receives/interprets user input

•         performs operations on the Model

•         triggers View update

Benefits:

–        better maintainability and testability of applications

–        ability to easily develop different kinds of UIs (e.g. console, GUI, …)

–        separation of different tasks in development

–        code reusability

Previous                                                                                                                                                                                           Next