Developing Enterprise Mashups

Mashup represents the future of web and applications development. Mashup has been the subject of many discussions since it has become the ideal way of developing an application.

Instead of using one programming language to develop a website or application, they use two or more programming languages.

The increasing demands of customers and clients push developers to look for other functions just to achieve the expected performance. Mashup is achieved by combining two or more programming languages especially when an API of a popular function is available.

API could be added to the existing application or website so that something better could be achieved. Combining APIs is a simplified mashup which is now the usual practice.

Mashup even became a byword for Web 2.0 since developers have started integrating different API with JavaScript as the vehicle for different applications.

On the other hand, Web 2.0 is closely associated with Ajax since Ajax could provide interactive applications and its integration with API. That is why mashup and Ajax are constantly being talked about if the developers want to build an online application with the help of existing API.

Challenge in the Enterprise Mashup

Developing an application with the help of API is relatively easier with the help of JavaScript. But developing an application for enterprise with mashup is not really a popular practice yet.

Most of the business applications today use Java or .Net since they wanted to build an application that is not only known for being interactive but also robust with a proven performance.

Java and .Net have the ability to build an application that could easily interact with their users and with the help of a powerful server; the application is set to service users without interruption. But even with these abilities, Java and .Net are faced with the fact that applications should be developed really fast due to increasing customer demands.

Developing a new feature will take time and resources not to mention the manpower. The easier way is to have an API but enterprise is using Java and .Net so they are unable to use APIs.

The Solution in DWR

Luckily, there are frameworks that enable Java and .Net for different APIs. There is a particular group of frameworks that are geared in using Java and .Net for an Ajax based application. Some frameworks will convert a programming language into JavaScript. But this is not perfect for enterprise since it will inhibit faster development.

The solution then is something in between – a framework that will not convert Java but will enable it to be integrated with API.

That’s where DWR or Direct Web Remoting comes in. This type of framework is usually built for Java. This framework creates a JavaScript version while maintaining the Java version of the application. The idea of “remoting” uses Java as remote agent that controls the functions of its JavaScript counterpart.

The JavaScript, which becomes an Ajax based application, could be integrated with API therefore building a totally new application but with controls from Java. Development is a lot easier since frameworks are basically tools and API can just be added to the available JavaScript application.