1. Presented by,
R.Mujeebabeham
Final year,CSE.

2. SEQUENCES :
 Mashups Definition
 Types of Mashups
 Mashups vs Portals
 Business Mashups

3. SEQUENCES ...
Architectural aspects of Mashups

Some problems with mashups

Pro's and con's

How to build a Mashup?

The Mashup programming model


4. Mashup: Definition
“A mashup is a web application that combines
content from more than one source into an
integrated experience”
✔ The Web as a Platform
✔ Services, not packaged software
✔ Remixable data sources
✔ Building situational applications ad hoc

5. PICTORIAL REPRESENTATION:
User
User Request Data presentation
Mashup Data
website Manipulation
API Call API Call Data
Data
Website 2
Website 1

6. A Simple Example:
User
What are the available Map with available
flats near US? flats marked
Mashup
website
Request for Request for
available flat Flat list Area map
area map
list
Real estate website Google Map

7. Types of Mashups:
Map mashups'
Google maps virtual Earth Yahoo maps MapQuest
Search and shopping mashups'
BizRate PriceGrabber MySimon Froogle

8. Video and photo mashups'
News mashups'

9. Mashups vs Portals:
Portal Mashup
Older technology, extension Using newer, loosely
to traditional Web server defined "Web 2.0"
model using well defined techniques
approach
Traditionally content Content aggregation can
aggregation takes place on take place either on the
the server server or on the client
Aggregates presentation­ Can operate on pure
oriented markup fragments XML content and also on
(HTML, WML, VoiceXML, presentation­oriented
etc.) content (e.g., HTML)

10. Business Mashups:
Business mashups are useful for integrating

business and data services, as business
mashups technologies provide the ability to
develop new integrated services quickly.
To combine internal services with external
or personalized information, and to make
these services tangible to the business user
through user­friendly Web browser interfaces.

11. Architectural aspects of Mashups:
Architecturally, there are two styles of
mashups:
(i)Web­based and
(ii)server­based

12. (i)Web­based Mashups :
Use the user's Web browser to combine and

reformat the data
(ii)server­based Mashups:
 Analyze and reformat the data on a
remote server and transmit the data to
the user's browser in its final form

13. Some problems with mashups:

14. Some problems with mashups:
1.Mashups sit on the shoulders of others.
2.Build real applications? Developing a
proprietary data source is a high cost route
to differentiation.
3. Consumer processes are simple.
4. Consumer business models are tough on
mashups.

15. Pro's and con's:
(I) Pros:
 Information reuse
 More resources to play with
(ii) Cons:
 Network congestion
 Speed bottleneck
Danger of service failure

16. How to build a Mashup?
Prerequisites

Three steps
✔ Planning
✔ API sign­up
✔ Coding

17. Prerequisites:
Required
✔ Programming Language
✔ Web Programming
✔ XML Manipulation (XPath, XQuery, etc…)
Recommended
✔ Web authoring tools

18. Three steps:
Planning:

(I) Pick a subject:
A Mashup of What?
✔
Map + Real Estate?
Bookshop + Library Catalog?
More sources of data  More complicated
✔
(II) Decide your data sources:
Who is your data provider?
✔
Maps: Google maps, Yahoo maps, etc..
Online shopping: Amazon, EBay, etc..
✔ Usually language agnostic
✔ Varying complexity

19. Planning continu...
(III) Other concerns
✔ How much time do you have?
✔ Do you have a server to run it on?
✔ Which programming language?

20. API sign­up:

Sign­up for the API
✔
­Visit the homepage of your data source
and sign up
✔ Example:
http://www.google.com/apis/maps/

21. Coding:

­ API Call
● REST, XML­PRC, SOAP , Javascript
­ Data Manipulation
➢ To generate API requests
➢ To process API responses
➢ To represent data internally
­ Web programming
➢ Design UI for your page

22. The Mashup programming model:
Lightweight programming model

✔ Support lightweight programming models
that allow for loosely coupled systems
✔ Think syndication, not coordination
✔ Design for “hackability” and remixability

23. The Mashup programming model:
(II) What does this mean?
✔ Uncontrolled reuse
✔ Collaborative composition
✔ Internet­wide interoperability
✔ User­centric approach

24.
THANK YOU