Unit IV Part III

CSE407R01 – Cloud Computing
Unit IV
Multicloud Mashup Architecture and Service

Cloud Mashup Architecture for Agility and Scalability
Multicloud Mashup Service Architecture
Skyline Discovery of Mashup Services
Dynamic Composition of Mashup Services.
Dr. J. Sangeetha/SAP/CSE/SRC/SASTRA 1
Multicloud Mashup Architecture and Service
• A cloud mashup is composed of multiple services with

shared data sets and integrated functionalities.
• Example: the EC2 provided by Amazon Web Service
(AWS), the authentication and authorization services
provided by Facebook, and the MapReduce service
provided by Google can all be mashed up to deliver real-
time, personalized driving route recommendation
services.
• To discover qualified services and compose them with
guaranteed QoS, an integrated skyline query processing
method for building up cloud mashup applications is
proposed.
• A multicloud mashup appears as a web page or web
application chain.
• Multiple clouds use content from more than one source to
create a single new service displayed in a single graphical
interface.
• For example, a user could combine the addresses and
photographs of their library branches with a Google map to
create a map mashup. The term implies easy and fast
integration, frequently using open APIs.
• The main characteristics of a mashup are combination,
visualization, and aggregation.
• Mashups can be considered to have an active role in the
evolution of social software and Web 2.0.
• Mashup composition tools are usually simple enough to be
used by end users.
• The Open Mashup Alliance (OMA) is a nonprofit
consortium that promotes the adoption of mashup solutions
in the enterprise through the evolution of enterprise mashup
standards like Enterprise Mashup Markup Language
(EMML).
• Enterprise mashup usage is expected to grow tenfold over
the next five years.
• The initial members of the OMA include Adobe Systems,
Hewlett-Packard, and Intel, and some technology users like
Bank of America and Capgemini.
• The OMA creates an open and vibrant market for
competing runtimes, mashups, and an array of important
aftermarket services.
Cloud Mashup Architecture for Agility and Scalability
• Hybrid cloud computing leverage occurs on both public

and private clouds.
• Cloud mashup was greatly inspired by using multiple
clouds to share the data sets and workload in colocation
cloud applications.
• In a recent study of 1,000 IT executives by the Hybrid
Hive, a news site sponsored by Fujitsu and several other
partners, hybrid clouds are becoming commonplace.
• More than 40% of executive respondents reported that they
already have a hybrid IT environment in place, while 51%
are open to it.
• Man companies spend one third of their total IT budgets on
various types of clouds. Some 80% of IT executives
believe in the hybrid infrastructure for the future.
• Data privacy and security concerns are the major barriers to
applying hybrid clouds or accepting cloud mashup services.
• In developing a chain of web applications, web or cloud
mashup combines data, presentation, or functionality from
two or more sources to create a new service chain.
• In cloud computing, the cloud has captured the computing
market with dynamic resource allocations from a pool of
VM resources.
• The AWS and GAE clouds differ not only in their
functionalities but also can complement each other for
better purposes.
• This has triggered the idea of mashing up different clouds
toward building an intercloud or cloud of clouds more
dynamically.
• As a matter of fact, cloud mashup offers a more cost-
effective solution to new start-ups that do not want to
invest in cloud hardware and software to create their own
enterprise level data centers or private clouds.
The Idea of Cloud Mashup
• Any startup in today’s business world needs to keep its

operational costs low in the initial years.
• This allows such businesses to recover initial investments
quickly and post profits faster.
• Consider a startup company that works as a social
networking portal.
• It needs lots of data storage space and servers, not to
mention the associated cooling requirements and
infrastructure, Such as a physical building for housing the
equipment and power.
• This could be a moderate to huge initial investment on the
part of the company.
• One can use the pay-per-use models from public clouds
like AWS and GAE to quickly bring the business up to
speed.
• This not only ensures that the loss due to time-to-market is
reduced, but also improves the speed with which one can
unleash a new idea into the world of business.
• Mashup use is expanding in the business environment.
• Today’s mashups are typically dataflow systems with the
interaction scripted in languages like JavaScript or PHP.
• The Programmable Web site had, for example, over 2,00
APIs and 5,000 mashups reported in 2010
• Example: A Mashup Service over the AWS and GAE
Cloud Platforms
• The mashup design leverages Google’s web agility with the scaling
power of AWS EC2.
• This mashup helps a user to write agile software on the App Engine
and use the user inputs to perform parallel computing operations on
the AWS.
• Also, the creator can apply parallel computing operations to a user-
owned cluster as well.
• AWS is no very handy as a scalable web interface because the size
of EC has to be increased by the subscriber’s request.
• Also, the name server has to be built by the user to isolate the end-
server from becoming directly visible on the network. On the other
hand, Google is more cost effective in this aspect
Advantages
• A business computing platform need to deliver not only

scalable services but also the agility t0 survive competition
• A mashup can combine several platforms or APIs to
provide a wider scope of service that allows more
flexibility and agility t the users. These two advantages are
characterized below.
• Scalability on the EC2 virtual clusters:
– Scaling the implementation of MapReduce can be done in two
dimensions: problem size and virtual cluster size.
– For the cluster size, the USC experiments run the MapReduce from
1 VM node to 40 VM nodes on the EC2 infrastructure.
– Thus, scaling is well explored on the EC2 to yield scalable
performance.
• Agility in using the AppEngine interfaces:
– A mashup platform is built by combined use of Google App
Engine and Amazon Web Services, essentially using the web
interfaces by Google and the computing power from Amazon EC2.
– We use the Google App Engine to create a web page that is
capable of uploading documents to the App Engine.
– Then take the user-uploaded documents and run the MapReduce on
the EC2. At the end, the mashup sends the results back to Google
users.
Multicloud Mashup Service Architecture Types
• Business (or enterprise) mashups

– It define applications that combine their own resources,
applications, and data with other external web services.
– They focus data into a single presentation and allow for
collaborative action among businesses and developers.
– This works well for an agile development project, which requires
collaboration between the developers and the customer for
implementing the business requirements.
– Enterprise mashups are secure, visually rich web applications that
expose actionable information from diverse internal and external
information sources.
• Consumer mashups
– It combine data from multiple public sources in the browser and
organize it through a simple browser user interface (e.g., Wikipedia
Vision combines Google Maps and a Wikipedia API)
• Data mashups
– It opposite to the consumer mashups, combine similar types of
media and information from multiple sources into a single
representation.
– The combination of all these resources creates a new and distinct
web service that was not originally provided by either source.
• Mashup enablers have also been described as the service
and tool providers that make mashups possible.
• A mashup is enabled by a tool that transforms incompatible
IT resources into a form that allows them to be easily
combined.
• Mashup enablers allow powerful techniques and tools for
combining data and services to be applied to new kinds of
resources.
• For example, there is a tool for creating an RSS feed from a
spreadsheet.
• Many mashup editors include mashup enablers, for
example, Presto Mashup Connectors, Convertigo Web
Integrator, or Caspio Bridge.
• Mashup of Multiple Cloud Services in Healthcare
Applications
• Suppose each of the tasks handled by an infirmary service
is deployed on a separate cloud.
• The five cloud services form a mashup of integrated
healthcare services as identified by a directed acyclic graph
(DAG), as shown in Figure.
• The output of the workflow is the complete process up to
the satisfaction of the patient.
• Each task could be one service provided by one or more
web-/cloud-based platforms.
Mashup Architecture Specification
• Architecturally, there are two styles of mashups:

– web-based and server based.
• The web-based mashups use the user’s web browser to
combine and reformat the data.
• The 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.
• In both cases, the architecture of a mashup is divided into
three layers:
• Presentation layer:
– This is the user interface of mashups. The technologies used
include HTML/XHTML, CSS, JavaScript, Asynchronous
JavaScript and XML (Ajax).
• Web services:
– A product’s functionality can be access using API services.
Popular tools used are XMLHttpRequest, XML-RPC, JSONRPC,
SOAP, and REST.
• Data layer:
– This layer handles the data such as sending, storing, and receiving.
The tools are XML, JSON, and KML.
• The quality of composite web services in intercloud applications
can be greatly enhanced by fast and optimized skyline query
processing.
• Figure 5.21 illustrates the idea and summarizes the work in three
parts: skyline selection, similarity test, and service composition.
• We select skyline services based on block elimination partitioning
of the data space.
• The skyline may produce a large number of candidate services. To
discover the best choice in each skyline subspace, a skyline
relaxation method can be used to consider only the representatives
in each subspace.
• These three component service classes form a composite
cloud service.
• To reduce the composition time, similarity testing among
compatible skyline selections can be used in various
skyline sectors.
• The purpose is to remove redundancy using skyline
representatives.
• Finally, we compose the mashup service as an integrated
package for users.
• The QoS and quality of experience (QoE) specify the
desired performance requirements in the mashup services.
Quality of Mashup Service (QoMS)
• QoMS directly evaluates different performance metric

attributes of composite mashup services.
• Take the “online healthcar planner” as an example.
• One can consider the waiting time, service time, cost,
reputation, reliability, and availability for each task.
• The response time is a major factor of QoMS since it
accounts for the communication traffic when a user
accesses the services and has a large impact on the service
quality.
• The duration of composite service is neither the optimal
nor the actual duration.
Quality of Experience (QoE)
• How customers are satisfied with the solutions provided by the

composite service is a critical part of the evaluation of QoE
• The QoE is defined by the percentile satisfaction level of a service’s
solution.
• Each solution is given a score denoting the customer-specified
solution quality.
• The methods of scoring the solution quality fall into two categories:
– Statistics-based or Profile-based.
– The statistics-based methods score a solution from customer voting or
reviewing comments.
– The profile-based methods dynamically estimate a customer’s satisfaction
level using example pair comparison.
Thank you…

Unit IV Part III

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit IV Part III

Uploaded by

Copyright:

Available Formats

CSE407R01 – Cloud Computing

Multicloud Mashup Architecture and Service

• A cloud mashup is composed of multiple services with

• Hybrid cloud computing leverage occurs on both public

• Any startup in today’s business world needs to keep its

• A business computing platform need to deliver not only

• Business (or enterprise) mashups

• Architecturally, there are two styles of mashups:

• QoMS directly evaluates different performance metric

• How customers are satisfied with the solutions provided by the

You might also like