Difference Between Similar Terms and Objects

Difference Between MVC1 and MVC2

MVC1 vs MVC2

MVC is actually a design pattern than can be further categorized into two models: the MVC Model 1 and the MVC Model 2. Abbreviated, they are MVC1 and MVC2 which are both Java design models.

MVC2 is actually a more complex pattern where separation of the Presentation Control Logic and Application state is done. Hence, unlike MVC1 architecture, the Model 2 doesn’t come with page-centric properties. The Model 2 also has one controller which is responsible for all incoming requests, figures out what would come up next, and what view to display. On MVC2, the links of the JSP pages for the next phase or view would also pass through the controller as opposed to the MVC1 where a JSP page directly leads to a JSP page.

So basically, MVC1 is mostly composed of control elements utilizing JSP while MVC2 makes use of a JSP and Servlet which is believed to be better than Model 1 in providing user interface. MVC1 also uses Java beans for data retrieval.

The difference in the two models’ systems becomes obvious in how the pages are processed and viewed. To explain further, MVC1 starts off with the request being accepted by a JSP that works together with a Bean, the two combined processing the logic to produce results. The job is divided between the two as the Beans take the role of the Model while the JSP is not only the “Controller” but also the “View.” This type of direct access between pages makes the MVC1 model ideal for smaller applications.

On the other hand, the MVC2 is usually utilized for bigger or interactive applications because of its “centralization” feature. Unlike the MVC1 where the current page on display is the one that determines the next page to open, the MVC2 architecture makes use of the controller between the browser and the Servlet or the JSP pages. As mentioned, the controller acts as the main “passageway” in which requests pass through to pave the way for the next view. The Model 2 basically separates those JSP pages and Servlets from one another while the Model 1 keeps the two coupled throughout. Hence, the MVC2 is easier to manipulate for many users and is capable of supporting a more-complicated system.

Currently, though, very few applications make use of MVC1 as their architecture design. Since the demands for web browsing have come higher, it is the norm to utilize MVC2 in whatever programs are being made. Of course, the fact that MVC1 is endlessly simple means that it continues to be a favorite for study purposes. However, practical applications are no longer practiced as often as MVC2.

One of the common misconceptions today, though, includes the usage of MVC1 and MVC2. Most people believe that MVC2 is actually a new version of MVC, but the fact is that it is a subcategory or another way of approaching the process, hence the name Model 2. For this reason, the phrase MVC1 was coined to create a distinction between the two models.

Ideally, those who want to master software architecture should opt to study both aspects of MVC instead of just MVC2. This would provide a better understanding of the whole system considering that MVC1 was first introduced.


1.MVC2 makes use of a system controller while MVC1 doesn’t.

2.The MVC1 process goes from one JSP page to another, while MVC2 directs to a common panel before directing to another page.

3.The MVC1 is seldom used today and is mostly good for simple, stand-alone programs.

4.MVC2 is the most common architecture model being used today and is best for more complex systems.

Sharing is caring!

Search DifferenceBetween.net :

Email This Post Email This Post : If you like this article or our site. Please spread the word. Share it with your friends/family.

Leave a Response

Please note: comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.

Articles on DifferenceBetween.net are general information, and are not intended to substitute for professional advice. The information is "AS IS", "WITH ALL FAULTS". User assumes all risk of use, damage, or injury. You agree that we have no liability for any damages.

See more about :
Protected by Copyscape Plagiarism Finder