Difference Between MVC1 and MVC2

MVC1 and MVC2 are models that are a further categorisation of MVC (Model Controller View). They are two distinct types of programming or design models that are used to create web applications. MVC1 is a rather simple application model as compared to MVC2. The two also vary on several other grounds such as technology, advantages, and drawbacks. 

MVC1 vs MVC2

The main difference between MVC1 and MVC2 is that MVC1 has only one component responsible for collecting and receiving information. On the other hand, MVC2 has two distinct components to receive and collect information. Moreover, in the MVC1 model, there is an association between presentation and business logic. In contrast, the MVC2 isolates presentation from business logic. 

MVC1 is a web application designing model put in use for simple stand-alone programs. In this model, both the controller and model are JSP. In addition, there is a single component for receiving and collecting information.  Although the MVC1 model offers easy understandability, the model is time-consuming and hard to extend. 

MVC2 is a complex version of the Model Controller View which is used to design web applications.  MVC2 model consists of three components: model, view, and controller. In addition, the model allows for isolation of the presentation logic from business logic. MVC1 is easy to test, maintain, and extend; it enables a separation of concerns effectively. 

Comparison Table Between MVC1 and MVC2 

What is MVC1?

Model 1 is an easy and quick design model to develop web applications. It has a simple architectural structure which makes it easily understandable. MVC1 uses JSP technology to design web applications. An advantage of JSP is that it allows easy separation of presentation and business logic, a problem often incurred with Servlet technology. 

In the MVC1 model, the browser sends a request for the JSP page, which accesses Java Bean. The Java Bean then invokes business logic, and connects to the database, thereafter saving information. Finally, a response is sent to the browser which is generated by JSP. However, there are very few applications that make use of the MVC1 architecture model. 

In the MVC1 model, both the controller and model are JSP. In addition, only one component is responsible for receiving and sending responses in the MVC1 model. This model has a practical application for simple stand-alone programs. Although the MVC1 model offers easy understandability, it has some drawbacks. 

The MVC1 model is time-consuming because an individual has to develop custom tags in JSP to avoid using a scriptlet tag. Another drawback of this model is that it is difficult to extend. Therefore, the MVC1 model is accessible for small applications rather than longer ones. In conclusion, MVC1 is an ideal model only for study purposes today.

What is MVC2?

MVC2 is a subcategory of MVC that has a relatively complex design model. The model consists of two components for receiving and sending responses. In addition, the model allows for isolation of the presentation logic from business logic. As a result, both the web designer and developer can access the web application simultaneously.

Based on the Model View Controller, the MVC2 model consists of three components that are model, view, and controller. The model serves the purpose of representing the business logic and stage data of the application. The view component represents the presentation, and the controller receives inputs. It then commands the Model/View to change according to the instructions. 

The MVC2 model offers several advantages. It is easy to test, maintain, and extend. In addition, it allows for a separation of concerns in an effective manner. However, there is one drawback. The user needs to write the controller code himself. A Change in the comptroller code then requires a recompilation of class redeployment of the application. 

In the MCV1 model, the controller uses servlet technology, and the model is a java class. The MVC1 model allows for the reusability of components. By far, it is one of the most common design models for the creation of web applications. 

Main Differences Between MVC1 and MVC2

1. MVC1 is a programming model which has a use in designing web applications for simple stand-alone programs. In contrast, MVC2 is a design model which has practical use in programming relatively larger web applications. 
2. MVC1 model is widely used for study purposes. On the other hand, the MVC2 model is popularly used to create web applications today. 
3. While MVC1 uses only JSP technology, MVC2 uses both JSP and Servlet technology.
4. MVC1 model associates the presentation logic with business logic. In contrast, the MVC2 model isolates presentation logic from business logic. 
5. MVC1 model doesn’t allow for the reusability of components. On the other hand, the MVC2 model allows for the reusability of components. 

Conclusion

The level of complexity, technology, reusability of components, and advantages of both the MVC1 and MVC2 models vary immensely. While MVC1 is easy to understand and use, the MVC2 model is relatively complex. In addition, the MVC1 model employs only JSP technology. On the other hand, MVC2 employs Java class and servlet technology. 

MVC1 model doesn’t allow reusability of components. In contrast, MVC2 offers the reusability of components. While the MVC1 model is well-suited for study purposes, the MVC2 model is currently used on a massive scale. Thus, in conclusion, MVC1 and MVC2 are models of varying characteristics and architecture. 

References

1. https://www.researchgate.net/profile/Praveen-Gupta-12/publication/49619227_MVC_Design_Pattern_for_the_multi_framework_distributed_applications_using_XML_spring_and_struts_framework/links/5672564e08ae54b5e462aac5/MVC-Design-Pattern-for-the-multi-framework-distributed-applications-using-XML-spring-and-struts-framework.pdf 
2. http://infocomp.dcc.ufla.br/index.php/INFOCOMP/article/view/242