Assignment 1: Mashup - Web Application
1. Introduction of Mashup:
It first appeared in music, which basically means mixing different types of music to create
different sound effects. The term then applied in Web 2.0, whereas mashup can be a webpage or
a web application that integrates contents such as data, presentation, or functionality from
different sources to create a new service. An interactive web application that take content form
different sources and present them in entirely new and unique manner.
2. Types of Mashups:
A. Business mashups: These are web applications that integrate their own content, used
to allow collaborative action among businesses and developers. It is secure and
usually visually mash web applications that expose actionable information from
diverse internal and external information sources.
B. Consumer mashups: These are integrate different visualizations and data elements
from multiple public sources to create a simple browser user interface that is more
appealing consumption of information. This is the most common type of mashup that
aimed at the general public.
C. Data mashups: It is opposites from consumer mashup. It integrates the same data
level. Whether it is integrating files, database, external web service APIs from
different multiple sources into a single representation.
3. Three layers that mashups are composed of:
a. Presentation or User Interaction Layer
b. Web Services
c. Data Pros & Cons:
i. Advantage:
1. It allows for the reuse of existing applications.
2. Time saving, it able to a more rapidly develop applications.
3. The development of a mashup does not require the user to have
extenuate IT or programming skills.
4. The cost of application development is reduced greatly.
ii. Disadvantage:
1. A user has no control over the quality or the features in the
application component they are implementing.
2. Scalability.
3. There is no guarantee that the service you are implementing will be
able to accommodate the traffic your website will get if it grows
bigger.
4. The contents used in the mashup service are not guaranteed be
secure.
5. There are no standards for the development or application of a
mashup, so these poses yet another difficulty in designing and
implementing security mechanisms to ensure the integrity of the
data being used,
4. Genres of Mashup:
a. Mapping mashups — example: Google maps API
b. Video & photo mashups — example: Flick & Picasa with API
c. Search & shopping mashups — example: eBay & Amazon Examples of Mashups
sites: 1. ChicagoCrime.org 2. TuneGlue 3. MapLarge
5. Conclusion:
Web portals, being a feature of what is now called Web 1.0, were developed as a way to
aggregate information from many resources into one unified format. Portals are developed under
the traditional web server model which uses “portlets”, a web application with a standardized
API to observe and process information in real-time and generate a markup representation of that
information. It will then aggregate the information typically by displaying several non-
overlapping windows, each window being managed by a portlet.
The development of mash-ups as a means of integrating data from different sources was brought
on by that emergence of powerful client side web software. The leading example of one such
technology is AJAX (Asynchronous JavaScript and XML).
Mash-ups provide the user with a much more customable and interactive interface to data as they
are not based on the read and update event models of portals which are defined through specific
portlet APIs.
Organization within mashup architecture ts essential in ensuring that it will deliver the necessary
functionalities quickly and efficiently and using the appropriate protocols and design principles
will enable mashups to be designed quicker.
