ASP.NET V.S. JSP which gives a better MVC implementation

by Salvador A
One of the major problems with a growing World wide web is the number of users and second the number of request being sent out by all of those users. To solve this problem their is a type of “website” implementation called MVC, which stands for The Model View Controller, design pattern. This type of design pattern aims to split up basic HTML into separate modules that each perform a specific task and create an overall better and faster web experience. By separating the modules, they are able to isolate the user interface logic from the business logic. The point here is that you no longer haveĀ  to perform major test when changing some user UI, instead since they are isolated from each other you will know that a change in one will not affect the other, thus you do not have to spend resources back tracking possible errors. The data provided showed that a MVC implementation in ASP.NET was better, the main point behind ASP.NET being better was that it is loosely implemented and thus made it easier for any programmer to implement the MVC. While JSP was also a direct implementation of MVC its major flaw was that it was difficult for programmers to implement.

This article provided a table with the pros of each type of MVC implementation and each one of the categories ASP.NET won. This was because of its ease of use, having a master page made it easier to handle all types of request. While in reality the JSP implementation was correct with its centralized controller as the article stated it was just more of a hassle to implement than ASP.NET using Visual Studio. Once again we see that any time there can be an easier implementation of a product everyone will prefer that one to the “proper” implementation.


Fawaz A. Masoud, Dana H. Halabi and Deema H. Halabi.(2006 October 16).ASP.NET AND JSP FRAMEWORKS IN MODEL VIEW CONTROLLER IMPLEMENTATION. Retrieved from :

2 thoughts on “ASP.NET V.S. JSP which gives a better MVC implementation”

  1. I have not used Visual Studio in several years, and I never used it for building websites, so I had some difficulty initially grasping the concept of the master page when used in conjunction with a css file. After playing with it a little bit during our current project, I have started to understand the thinking behind using master pages as it does make the job of building/modifying sites much easier once one gets the drift of how the pages interact with one another. Considering all of this, I do see how Microsoft's ASP can be considered to outperform JSP.

  2. It takes getting used to, but I like the master page idea. It lets you cut out a whole lot of stuff you don’t need, and makes everything quicker.

Comments are closed.