Skip to main content

MVC and AJAX

Most web based J2EE application use an MVC framework like Struts, Velocity, Spring, etc. All these frameworks provide a Controller which intercepts requests from the client and determines the model element to invoke. Will this change once AJAX becomes more widely adopted? When we use AJAX, all requests first go to the AJAX engine which in turn makes an HTTP request to the server. The response is monitored by a callback function which acts upon the response when it is recieved.

A reason why an alternative architecture may emerge, is because of the shortcomings of using an MVC framework. Despite of the advantages that are promised by some of these frameworks, they do have many strings attached. Once you use a framework, you have to do things *their* way. They very often influence the application's architecture also. Making the architecture flexible enough to replace the framework has to be done by creating a layer of abstraction between the application and the framework. This adds to the complexity and cost of the application. Most MVC frameworks cannot be used without a rather steep learning curve. This problem is even more pronounced when a team has to invest time in learning different frameworks for different clients. I have known people to take as much as a month to get comfortable with Struts, which is quite a huge time investment.

However frameworks do have their advantages also, which is why they are probably so popular. The biggest advantage is reusing the plumbing code of the framework, and declarative programming which most frameworks support. Declarative programming however has it's own drawbacks. As the application grows in size the configuration files tend to become very unwieldy.

Frameworks are not necessarily bad. I think a balance has to be created between using a framework and creating our own code. Perhaps light weight frameworks will work best. I used a big time user of frameworks, but over the years I have realized that the productivity benefit of the plumbing code comes at the cost of a steep learning curve. This is particularly painful when we have to undergo the learning curve of an entire framework for using just a part of it.

An architecture that might emerge is one in which the Controller resides on the client (written in Javascript) as opposed to the server. It receives the request from the AJAX engine and determines the appropriate webservice to invoke. The webservice returns an XML to which an XSL is applied and the result is displayed in the browser. Such an architecture removes the need of complex MVC frameworks and uses a simple controller written in Javascript.

I am not sure if a light weight, client side MVC framework is what will be used in the future, but I do think there are advantages to such a design. I would like to know what people think. Based on the comments I will discuss pros and cons of such a design in the next few posts.

Comments

Popular posts from this blog

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb-1.8.0.7.jar org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- prismnet.com As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a