Home > Articles > Software Development & Management

Mashup Styles, Techniques, and Technologies

J. Jeffrey Hanson, author of Mashups: Strategies for the Modern Enterprise, points out some of the most widely used styles, techniques, and technologies to build mashups.
This chapter is from the book

To begin design work on a mashup, you must determine what is to be "mashed" together. Three high-level categories of items can be mashed together—user interface artifacts (presentation), data, and/or application functionality (processes). This might include HTML snippets, on-demand JavaScript to access an external API, web service APIs from one of your corporate servers, RSS feeds, and/or other data to be mixed and mashed within the application or pages. The implementation style, techniques, and technologies used for a given mashup depend on this determination. Once the items are determined, your development team can proceed with applying languages, processes, and methodologies to the application at hand.

In this chapter, I point out some of the most widely used styles, techniques, and technologies to build mashups for each of the three primary categories or items.

Determining the Technological Domain for a Mashup

Along with determining what is to be mashed, you must also determine the sources from which the mashup items will be accessed; the style, technologies, and techniques your staff needs to build the mashup; and what services you need to build or access to retrieve the necessary artifacts for your mashup.

Mashups rely on the ability to mix loosely coupled artifacts within a given technological domain. The requirements of the application determine what artifacts (UI, data, and/or functionality) will be needed to build the mashup.

From a high-level perspective, the technological domain as applied to mashups can be viewed as presentation-oriented, data-oriented, and process-oriented. Different languages, methodologies, and programming techniques apply to each technological domain.

As shown in Figure 1.1, mashup categories can be divided according to presentation artifacts, data, and application functionality/processes. Each of these categories requires specific skills and programming technologies, as discussed next.

Figure 1.1

Figure 1.1 Three primary mashup technological domains


A presentation-oriented mashup mixes different user interface (UI) artifacts together to create a new application or page. Typically, this type of mashup aims to create an application or page displaying UI artifacts in a manner similar to a conventional portal. That is, each artifact is to be displayed in a separate small area on an application pane or page in a segregated manner in relation to the other artifacts. Very little or no interaction takes place between the UI artifacts in a presentation-oriented mashup.

Technologies used in a presentation-oriented mashup can include

  • Gadgets and widgets—User interface components that can be placed on an application pane or page independent of other items on the application pane or page. Legacy definitions of widgets referred to them in a more fine-grained manner as applied to desktop components, for example, buttons, scrollbars, sliders, and toolbars. The definition has been expanded in relation to web pages and mashups to include components comprised of more complex and self-contained functionality such as a clock, calculator, weather information, and so on. Gadgets and widgets may or may not retrieve data from an external site.
  • On-demand JavaScript, JavaScript snippets, and badges—Small sections of JavaScript code that can be inserted within an application pane or page to create user interface components. Typically, the JavaScript relies on interaction with a web service API that returns data and functionality used to build the user interface artifact.
  • CSS/HTML/XHTML—Snippets that can be inserted to create segregated user interface components that can be reused without regard to the application domain.
  • Flash components/Java applets/ActiveX controls—Self-contained user interface components that rely on proprietary container technologies such as a virtual machine or runtime that is embedded within the application pane or browser page.

A presentation-oriented mashup is usually the easiest and quickest type of mashup to build. Since there is little or no interaction between the mashed items, the mashup developer can simply worry about placing the items on the application pane or page in the desired location with the desired UI theme.


Data-oriented mashups (in-process or out-of-process) involve combining data from one or more externally hosted sites together in an application pane or web page typically using scripting techniques and languages such as JavaScript, JScript, and others. In this type of mashup, data is returned from a site or server in the form of XML, RSS, JSON, Atom, and so on. Much of the data returned originates from data-oriented services sometimes referred to as Data-as-a-Service (DaaS). DaaS describes a data-oriented service API that can be called without relying on third-party processes or components between the service provider and the service consumer.

In-Process Data-Oriented Mashups

In-process data-oriented mashups rely on data being mixed together using application or browser technologies such as JavaScript, AJAX, or the Document Object Model (DOM). In this style of mashup data is retrieved from one or more sites/servers and used as values or configuration settings to build user interface artifacts within an application process or browser page.

Out-of-Process Data-Oriented Mashups

Out-of-process data-oriented mashups rely on data being mixed together using technologies such as Java, Python, Perl, C++, XML, and XSLT, to name a few. In this style of mashup data is retrieved from one or more sites/servers and used as values or configuration settings to create new data models within a server-side process or separate client-side process.


Process-oriented mashups (out-of-process) involve combining functionality together in one or more external processes using programming languages such as Java, PHP, Python, and C++. Mashups built for enterprise applications or web applications can involve frameworks such as JEE, .NET, and Ruby on Rails.

In a process-oriented mashup, functionality is combined using interprocess/interthread communication techniques such as shared memory, message queues/buses, remote procedure calls (RPC), and so on. Even though data is exchanged between processes and threads in a process-oriented mashup, the end result differs from a data-oriented mashup in that the data-oriented mashup seeks to derive new data models, whereas a process-oriented mashup seeks to derive new processes and/or services.

More often than not, enterprises require a hybrid approach when building a mashup. This is due to the number of disparate sources from which functionality and data are retrieved such as geocoding sites, RSS feeds, and corporate data stores.

So, when preparing to build a mashup you must first determine what is to be mashed, the technological domain in which to build the mashup, and the sources from which the mashup artifacts will be accessed. With this information in hand you can then determine whether your development staff possess the skills to employ the techniques and technologies needed to build the mashup. The skills of your staff have a big impact on the decision of which mashup style you choose. The following section discusses the reasons for choosing different mashup styles and/or domains.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020