CS6703 GRID AND CLOUD COMPUTING

Unit 1

UNIT I INTRODUCTION

Evolution of Distributed computing:

Scalable
computing
over
the
Internet Technologies for network
based systems clusters of
cooperative computers - Grid
computing Infrastructures cloud
computing - service oriented
architecture Introduction to
Grid Architecture and standards
Elements of Grid Overview 7/22/16
of

Distributed Computing
Definition
A distributed system consists of multiple

autonomous computers that communicate

through a computer network.
Distributed computing utilizes a network of
many computers, each accomplishing a portion
of an overall task, to achieve a computational
result much more quickly than with a single
computer.
Distributed computing is any computing that
involves multiple computers remote from each
other that each have a role in a computation
problem or information processing.
3

7/22/16

Introduction
A distributed system is one in which hardware

or software components located at

networked computers communicate and
coordinate their actions only by message
passing.
In the term distributed computing, the word
distributed means spread out
across space. Thus, distributed computing is
an activity performed on a spatially
distributed system.
These networked computers may be in the
same
room, same campus, same
country, or in different continents

7/22/16

Introduction
Agent
Cooperation

Agent

Agent

Cooperation
Distribution

Distribution

Cooperation

Distribution

Internet
Internet
Subscription

Agent
Distribution

Job Request

Resource
Management

Large-scale
Application

7/22/16

Motivation
Inherently distributed applications
Performance/cost
Resource sharing
Flexibility and extensibility
Availability and fault tolerance
Scalability
Network connectivity is increasing.
Combination of cheap processors often more

cost-effective than one expensive fast

system.
Potential increase of reliability.
6

7/22/16

History
1975 1985
Parallel computing was favored in the early
years
Primarily vector-based at first
Gradually more thread-based parallelism was
introduced
The first distributed computing programs were
a pair of programs called Creeper and Reaper
invented in 1970s
Ethernet that was invented in 1970s.
ARPANET e-mail was invented in the early
1970s and probably the earliest example of a
large-scale distributed application.
7

7/22/16

History
1985 -1995
Massively parallel architectures start rising and
message passing interface and other libraries
developed
Bandwidth was a big problem
The first Internet-based distributed computing
project was started in 1988 by the DEC System
Research Center.
Distributed.net was a project founded in 1997 considered the first to use the internet to
distribute data for calculation and collect the
results,
8

7/22/16

History
1995 Today
Cluster/grid architecture increasingly
dominant
Special node machines eschewed in favor of
COTS technologies
Web-wide cluster software
Google take this to the extreme (thousands of
nodes/cluster)
SETI@Home started in May 1999 - analyze
the radio signals that were being collected by
the Arecibo Radio Telescope in Puerto Rico.

7/22/16

Goal
Making Resources Accessible
Data sharing and device sharing

Distribution Transparency
Access, location, migration, relocation,

replication, concurrency, failure

Communication
Make human-to-human comm. easier. E.g.. :

electronic mail

Flexibility
Spread the work load over the available

machines in the most cost effective way

To coordinate the use of shared resources

To solve large computational problem
10

7/22/16

Characteristics
Resource Sharing
Openness
Concurrency
Scalability
Fault Tolerance
Transparency

11

7/22/16

Architecture
Client-server
3-tier architecture
N-tier architecture
loose coupling, ortight coupling
Peer-to-peer
Space based

12

7/22/16

Application
Examples of commercial application :
Database Management System
Distributed computing using mobile agents
Local intranet
Internet (World Wide Web)
JAVA Remote Method Invocation (RMI)

13

7/22/16

Distributed Computing Using Mobile

Agents
Mobile agents can be wandering around in a network

using free resources for their own computations.

14

7/22/16

Local Intranet
A portion of Internet that is separately administered &

supports internal sharing of resources (file/storage

systems and printers) is called local intranet.

15

7/22/16

Internet
The Internet is a global system of interconnected

computer networks that use the standardized Internet

Protocol Suite (TCP/IP).

16

7/22/16

JAVA RMI
Embedded in language Java:-

Object variant of remote procedure call

Adds naming compared with RPC (Remote Procedure Call)
Restricted to Java environments

17

RMI Architecture

7/22/16

Categories of Applications in distributed

computing
Science
Life Sciences
Cryptography
Internet
Financial
Mathematics
Language
Art
Puzzles/Games
Miscellaneous
Distributed Human Project
Collaborative Knowledge Bases
18

Charity

7/22/16

Advantages
Economics: Computers harnessed together give a better
price/performance ratio than mainframes.
Speed: A distributed system may have more total computing
power than a mainframe.
Inherent distribution of applications: Some applications are inherently distributed. E.g., an ATMbanking application.
Reliability: If one machine crashes, the system as a whole can still
survive if you have multiple server machines and multiple
storage devices (redundancy).
Extensibility and Incremental Growth: Possible to gradually scale up (in terms of processing
power and functionality) by adding more sources (both
hardware and software). This can be done without
disruption to the rest of the system.

19

7/22/16

Disadvantages
Complexity : Lack of experience in designing, and
implementing a distributed system. E.g. which
platform (hardware and OS) to use, which
language to use etc.
Network problem: If the network underlying a distributed system

saturates or goes down, then the distributed

system will be effectively disabled thus negating
most of the advantages of the distributed system.

Security: Security is a major hazard since easy access to

data means easy access to secret data as well.

20

7/22/16

Issues and Challenges

Heterogeneity of components :variety or differences that apply to computer

hardware, network, OS, programming language

and implementations by different developers.
All differences in representation must be deal
with if to do message exchange.
Example : different call for exchange message
in UNIX different from Windows.
Openness:System can be extended and re-implemented in
various ways.
Cannot be achieved unless the specification and
documentation are made available to software
developer.
The most challenge to designer is to tackle the
complexity of distributed system; design by
different people.
21

7/22/16

Issues and Challenges cont

Transparency:Aim : make certain aspects of distribution

are invisible to the application

programmer ; focus on design of their
particular application.
They not concern the locations and
details of how it operate, either replicated
or migrated.
Failures can be presented to application
programmers in the form of exceptions
must be handled.

22

7/22/16

Issues and Challenges cont

Transparency:This concept can be summarize as shown

in this Figure:

23

7/22/16

Issues and Challenges cont

Security:Security for information resources in

distributed system have 3 components :

a. Confidentiality : protection against disclosure
to unauthorized individuals.
b. Integrity : protection against
alteration/corruption
c. Availability : protection against interference
with the means to access the resources.
The challenge is to send sensitive

information over Internet in a secure

manner and to identify a remote user or
other agent correctly.
24

7/22/16

Issues and Challenges cont..

Scalability :Distributed computing operates at many

different scales, ranging from small

Intranet to Internet.
A system is scalable if there is significant
increase in the number of resources and
users.
The challenges is :
a. controlling the cost of physical resources.
b. controlling the performance loss.
c. preventing software resource running out.
d. avoiding performance bottlenecks.

25

7/22/16

Issues and Challenges cont

Failure Handling :Failures in a distributed system are partial

some components fail while others can

function.
Thats why handling the failures are
difficult

a. Detecting failures : to manage the presence of

failures cannot be detected but may be suspected.
b. Masking failures : hiding failure not guaranteed in
the worst case.

Concurrency :Where applications/services process

26

concurrency, it will effect a conflict in

operations with one another and produce
inconsistence results.
Each resource must be designed to be safe

7/22/16

Conclusion
The concept of distributed computing is the

most efficient way to achieve the

optimization.
Distributed computing is anywhere : intranet,
Internet or mobile ubiquitous computing
(laptop, PDAs, pagers, smart watches, hi-fi
systems)
It deals with hardware and software systems,
that contain more than one processing /
storage and run in concurrently.
Main motivation factor is resource sharing;
such as files , printers, web pages or
database records.
27 Grid computing and cloud computing are

7/22/16

Grid Computing
Grid computing is a form of distributed computing whereby a
"super and virtual computer" is composed of a cluster of
networked, loosely coupled computers, acting in concert to
perform very large tasks.
Grid computing (Foster and Kesselman, 1999) is a growing
technology that facilitates the executions of large-scale
resource intensive applications on geographically distributed
computing resources.
Facilitates flexible, secure, coordinated large scale resource
sharing among dynamic collections of individuals, institutions,
and resource
Enable communities (virtual organizations) to share
geographically distributed resources as they pursue common
goals
28

7/22/16

Criteria for a Grid:

Coordinates resources that are not subject to
centralized control.
Uses standard, open, general-purpose protocols
and interfaces.
Delivers nontrivial qualities of service.
Benefits
Exploit Underutilized resources
Resource load Balancing
Virtualize resources across an enterprise
Data Grids, Compute Grids

Enable collaboration for virtual organizations

29

7/22/16

Grid Applications
Data and computationally intensive applications:
This technology has been applied to computationally-intensive
scientific, mathematical, and academic problems like drug
discovery, economic forecasting, seismic analysis back office
data processing in support of e-commerce
A chemist may utilize hundreds of processors to screen
thousands of compounds per hour.
Teams of engineers worldwide pool resources to analyze
terabytes of structural data.
Meteorologists seek to visualize and analyze petabytes of
climate data with enormous computational demands.
Resource sharing
Computers, storage, sensors, networks,
Sharing always conditional: issues of trust, policy, negotiation,
payment,
Coordinated problem solving
distributed data analysis, computation, collaboration,
30

7/22/16

Grid Topologies

31

Intragrid
Local grid within an organization
Trust based on personal contracts
Extragrid
Resources of a consortium of
organizations
connected through a (Virtual) Private
Network
Trust based on Business to Business
contracts
Intergrid
Global sharing of resources through the
internet
7/22/16
Trust based on certification

Computational Grid
A computational grid is a hardware and software
infrastructure that provides dependable, consistent,
pervasive, and inexpensive access to high-end
computational capabilities.
The Grid: Blueprint for a New Computing
Infrastructure, Kesselman & Foster
Example : Science Grid (US Department of Energy)

32

7/22/16

Data Grid
A data grid is a grid computing system that deals

with data the controlled sharing and

management of large amounts of distributed
data.

Data Grid is the storage component of a grid

environment. Scientific and engineering applications

require access to large amounts of data, and often
this data is widely distributed. A data grid provides
seamless access to the local or remote data required
to complete compute intensive calculations.
Example :
Biomedical informatics Research Network (BIRN),
the Southern California earthquake Center (SCEC).

33

7/22/16

Methods of Grid Computing

Distributed Supercomputing
High-Throughput Computing
On-Demand Computing
Data-Intensive Computing
Collaborative Computing
Logistical Networking

34

7/22/16

Distributed Supercomputing

Combining multiple high-capacity

resources on a computational grid into a

single, virtual distributed supercomputer.
Tackle problems that cannot be solved on

a single system.

35

7/22/16

High-Throughput Computing
Uses the grid to schedule large numbers

of loosely coupled or independent tasks,

with the goal of putting unused
processor cycles to work.

On-Demand Computing

36

Uses grid capabilities to meet short-term

requirements for resources that are not
locally accessible.
Models real-time computing demands.
7/22/16

Collaborative Computing

Concerned primarily with enabling and

enhancing human-to-human interactions.

Applications are often structured in terms
of a virtual shared space.

Data-Intensive Computing

37

The focus is on synthesizing new information

from data that is maintained in geographically
distributed repositories, digital libraries, and
databases.
Particularly useful for distributed data mining.
7/22/16

Logistical Networking
Logistical networks focus on exposing

storage resources inside networks by

optimizing the global scheduling of data
transport, and data storage.
Contrasts with traditional networking, which
does not explicitly model storage resources
in the network.
high-level services for Grid applications
Called "logistical" because of the analogy it
bears with the systems of warehouses,
depots, and distribution channels.
38

7/22/16

P2P Computing vs Grid Computing

Differ in Target Communities

Grid system deals with more complex,

more powerful, more diverse and highly

interconnected set of resources than
P2P.
VO

39

7/22/16

A typical view of Grid environment

Grid InformationGrid
Service system
collects the details of
the available Grid
resources and passes
the information to
the resource broker.

Information Service

Details of Grid
resources

1
2

Grid
application

User

Computation
result

A User sends
computation or data
intensive application
to Global Grids in
order to speed up the
execution of the
application.
40

Computational
4 jobs
Processed jobs

Resource Broker

A Resource Broker
distribute the jobs in an
application to the Grid
resources based on users
QoS requirements and
details of available Grid
resources for further
executions.

Grid Resources

Grid Resources (Cluster,

PC, Supercomputer,
database, instruments,
etc.) in the Global Grid
execute the user jobs.
7/22/16

Grid Middleware
Grids are typically managed by grid ware -

a special type of middleware that enable sharing and

manage grid components based on user requirements
and resource attributes (e.g., capacity, performance)
Software that connects other software components or
applications to provide the following functions:
Run applications on suitable available resources
Brokering, Scheduling
Provide uniform, high-level access to resources
Semantic interfaces
Web Services, Service Oriented Architectures
Address inter-domain issues of security, policy, etc.
Federated Identities
Provide application-level status
monitoring and control

41

7/22/16

Middleware
Globus chicago Univ
Condor Wisconsin Univ High throughput

computing
Legion Virginia Univ virtual workspacescollaborative computing
IBP Internet back pane Tennesse Univ
logistical networking
NetSolve solving scientific problems in
heterogeneous env high throughput &
data intensive
42

7/22/16

Two Key Grid Computing Groups

The Globus Alliance (www.globus.org)
Composed of people from:
Argonne National Labs, University of Chicago, University of
Southern California Information Sciences Institute, University
of Edinburgh and others.
OGSA/I standards initially proposed by the Globus Group
The Global Grid Forum (www.ggf.org)
Heavy involvement of Academic Groups and Industry
(e.g. IBM Grid Computing, HP, United Devices, Oracle, UK eScience Programme, US DOE, US NSF, Indiana University,
and many others)
Process
Meets three times annually
Solicits involvement from industry, research groups, and
academics
43

7/22/16

Some of the Major Grid Projects

Name

URL/Sponsor

Focus

EuroGrid, Grid
Interoperability
(GRIP)

eurogrid.org
European Union

Fusion
Collaboratory

fusiongrid.org
Create a national computational
DOE Off. Science collaboratory for fusion research

Globus Project

globus.org
DARPA, DOE,
NSF, NASA,
Msoft

Research on Grid technologies;

development and support of Globus
Toolkit; application and deployment

GridLab

gridlab.org
European Union

Grid technologies and applications

GridPP

gridpp.ac.uk
U.K. eScience

Create & apply an operational grid within

the U.K. for particle physics research

Grid Research
Integration Dev. &
Support Center

grids-center.org
NSF

Integration, deployment, support of the

NSF Middleware Infrastructure for
research & education

44

Create tech for remote access to super

comp resources & simulation codes; in
GRIP, integrate with Globus Toolkit

7/22/16

Grid Architecture

45

7/22/16

The Hourglass Model

Focus on architecture issues
Propose set of core services

Applications

Diverse global services

as basic infrastructure
Used to construct high-level,
domain-specific solutions
(diverse)
Core
Design principles
services
Keep participation cost low
Enable local control
Support for adaptation
IP hourglass model
46

Local OS

7/22/16

Layered Grid Architecture

(By Analogy to Internet Architecture)

Coordinating multiple resources:

ubiquitous infrastructure services,
app-specific distributed services

Collective

Application

Sharing single resources:

negotiating access, controlling use

Resource

Talking to things: communication

(Internet protocols) & security

Connectivity

Transport
Internet

Controlling things locally: Access

to, & control of, resources

Fabric

Link

47

7/22/16

Internet Protocol Architecture

Application

Example:
Data Grid Architecture
App

Discipline-Specific Data Grid Application

CollectiveCoherency control, replica selection, task management,

(App) virtual data catalog, virtual data code catalog,
CollectiveReplica catalog, replica management, co-allocation,
(Generic)certificate authorities, metadata catalogs,
Resource Access to data, access to computers, access to network
performance data,
Connect Communication, service discovery (DNS), authentication,
authorization, delegation
Fabric

48

Storage systems, clusters, networks, network caches,

7/22/16

Simulation tools
GridSim job scheduling
SimGrid single client multiserver

scheduling
Bricks scheduling
GangSim- Ganglia VO
OptoSim Data Grid Simulations
G3S Grid Security services Simulator
security services

49

7/22/16

Simulation tool

50

GridSim is a Java-based toolkit for

modeling, and simulation of distributed
resource management and scheduling for
conventional Grid environment.

GridSim is based on SimJava, a general

purpose discrete-event simulation package
implemented in Java.

All components in GridSim communicate

with each other through message passing
operations defined by SimJava.
7/22/16

Salient features of the GridSim

It allows modeling of heterogeneous types of

51

resources.
Resources can be modeled operating under
space- or time-shared mode.
Resource capability can be defined (in the form
of MIPS (Million Instructions Per Second)
benchmark.
Resources can be located in any time zone.
Weekends and holidays can be mapped
depending on resources local time to model
non-Grid (local) workload.
Resources can be booked for advance
reservation.
Applications with different parallel
7/22/16
application models can be simulated.

Salient features of the GridSim

Application tasks can be heterogeneous and they

52

can be CPU or I/O intensive.

There is no limit on the number of application
jobs that can be submitted to a resource.
Multiple user entities can submit tasks for
execution simultaneously in the same resource,
which may be time-shared or space-shared. This
feature helps in building schedulers that can use
different market-driven economic models for
selecting services competitively.
Network speed between resources can be
specified.
It supports simulation of both static and dynamic
schedulers.
Statistics of all or selected operations can be
recorded and they can be analyzed using
7/22/16
GridSim statistics analysis methods.

A Modular Architecture for GridSim Platform and Components.

Application, User, Grid Scenarios input and Results
Appn Conf

Res Conf

User Req

Grid Sc

Output

Grid Resource Brokers or Schedulers

GridSim Toolkit
Appn
modeling

Res entity

Info serv

Job mgmt

Res alloc

Statis

Resource Modeling and Simulation

Single
CPU

SMPs

Clusters

Load

Netw

Reservation

Basic Discrete Event Simulation Infrastructure

SimJava
Distributed SimJava
Virtual Machine
53

PCs

Workstation

SMPs

Clusters

Distributed
7/22/16
Resources

Web 2.0, Clouds, and Internet of Things

HPC: High - Performance Computing HTC: High - Throughput

Computing
P2P: Peer to Peer

54

MPP: Massively Parallel Processors

7/22/16

What is a Service Oriented

Architecture?

55

What is a Service Oriented Architecture (SOA)?

A method of design, deployment, and

management of both applications and the

software infrastructure where:
All software is organized into business services

that are network accessible and executable.

Service interfaces are based on public
standards for interoperability.

56

Key Characteristics of SOA

Quality of service, security and

performance are specified.

Software infrastructure is responsible for
managing.
Services are cataloged and discoverable.
Data are cataloged and discoverable.
Protocols use only industry standards.

57

What is a Service?
A Service is a reusable component.
A Service changes business data from one

state to another.
A Service is the only way how data is
accessed.
If you can describe a component in WSDL, it is
a Service.

58

Information Technology is Not

SOA
Business Mission
Information Management

SOA

Information Systems
Systems Design
Computing & Communications

59

Informatio
n
Technology

Why Getting SOA Will be Difficult

Managing for Projects:
Software: 1 - 4 years
Hardware: 3 - 5 years;
Communications: 1 - 3 years;
Project Managers: 2 - 4 years;
Reliable funding: 1 - 4 years;
User turnover: 30%/year;
Security risks: 1 minute or less.

Managing for SOA:

Data: forever.
Infrastructure: 10+ years.

60

Why Managing Business Systems is

Difficult?
40 Million lines of code in Windows XP is

unknowable.
Testing application (3 Million lines) requires
>1015 tests.
Probability correct data entry for a supply
item is <65%.
There are >100 formats that identify a
person in DoD.
Output / Office Worker: >30 e-messages
/day.
61

How to View Organizing for

SOA
PERSONAL LEVEL

Private Applications and Files

Privacy and
I ndividual
Security Barrier

Applications
Security Barrier

Graphic InfoWindow, Personal Tools, Inquiry Languages

Customized Applications, Prototyping Tools, Local
Applications and Files

Applications Development & Maintenance

VARIETY HERE
LOCAL LEVEL

APPLICATION LEVEL

Business
Security Barrier

Service A
Process
Security Barrier

Service B

OSD

Functional Process A
Functional Process B
Functional Process C
Functional Process D
Corporate Policy, Corporate Standards, Reference Models,
Data Management and Tools, Integrated Systems
Configuration Data Base, Shared Computing and
Telecommunications
Industry Standards, Commercial Off-the-Shelf
Products and Services

62

BUSINESS LEVEL

PROCESS LEVEL

ENTERPRISE LEVEL

STABILITY HERE
GLOBAL LEVEL

SOA Must Reflect Timing

Private Applications and Files

PERSONAL

Graphic InfoWindow, Personal Tools, Inquiry Languages

Customized Applications, Prototyping Tools, Local
Applications and Files

Applications Development & Maintenance

Business A

Business B

Infrastructure
Support

LOCAL

APPLICATION

SHORT TERM
ADAPTABILITY &
TECHNOLOGY
SIMPLICITY

BUSINESS

Functional Process A
Functional Process B
Functional Process C
Functional Process D
Corporate Policy, Corporate Standards, Reference Models,
Data Management and Tools, Integrated Systems
Configuration Data Base, Shared Computing and
Telecommunications, Security and Survivability
Industry Standards, Commercial Off-the-Shelf
Products and Services

63

PROCESS

ENTERPRISE

GLOBAL

LONG TERM
STABILITY &
TECHNOLOGY
COMPLEXITY

SOA Must Reflect Conflicting Interests

Personal
Local
Organizations
Missions
Enterprise
64

Organization of Infrastructure Services

Infrastructure
Services
(Enterprise Information)

Data
Services

65

Security
Services

Computing Communication Application

Services
Services
Services

Organization of Data Services

Data
Services

Discovery
Services

66

Management Collaboration Interoperability

Services
Services
Services

Semantic
Services

Data Interoperability Policies

Data are an enterprise resource.
Single-point entry of unique data.
Enterprise certification of all data

definitions.
Data stewardship defines data custodians.
Zero defects at point of entry.
De-conflict data at source, not at higher
levels.
Data aggregations from sources data, not
from reports.

67

Data Concepts
Data Element Definition
Text associated with a unique data element within a data

dictionary that describes the data element, give it a

specific meaning and differentiates it from other data
elements. Definition is precise, concise, non-circular, and
unambiguous.
(ISO/IEC 11179 Metadata Registry specification)
Data Element Registry
A label kept by a registration authority that describes a

unique meaning and representation of data elements,

including registration identifiers, definitions, names, value
domains, syntax, ontology and metadata attributes. (ISO
11179-1).

68

Data and Services Deployment Principles

Data, services and applications belong to

the Enterprise.
Information is a strategic asset.
Data and applications cannot be coupled to
each other.
Interfaces must be independent of
implementation.
Data must be visible outside of the
applications.
Semantics and syntax is defined by a
community of interest.
69
Data
must be understandable and trusted.

Organization of Security
Services
Security
Services

Transfer
Services

70

Protection
Services

Certification
Services

Systems
Assurance

Authentication

Services

Security Services = Information Assurance

Conduct Attack/Event Response
Ensure timely detection and appropriate response to

attacks.
Manage measures required to minimize the
networks vulnerability.

Secure Information Exchanges

Secure information exchanges that occur on the

network with a level of protection that is matched to

the risk of compromise.

Provide Authorization and Non-Repudiation

Services
Identify and confirm a user's authorization to access

the network.
71

Organization of Computing Services

Computing
Services

Computing
Facilities

72

Resource
Planning

Control &
Quality

Configuration
Services

Financial
Management

Computing Services
Provide Adaptable Hosting Environments
Global facilities for hosting to the edge.
Virtual environments for data centers.

Distributed Computing Infrastructure

Data storage, and shared spaces for

information sharing.

Shared Computing Infrastructure Resources

Access shared resources regardless of access

device.

73

Organization of Communication
Services
Communication
Services

Spectrum
Interoperability
Management
Services

74

Connectivity
Arrangements

Continuity of
Services

Resource
Management

Network Services
Implementation
From point-to-point communications (push

communications) to network-centric
processes (pull communications).
Data posted to shared space for retrieval.
Network controls assure data
synchronization and access security.

75

Communication Services
Provide Information Transport
Transport information, data and services

anywhere.
Ensures transport between end-user devices
and servers.
Expand the infrastructure for on-demand
capacity.

76

Organization of Application Services

Application
Services

Component
Repository

77

Code Binding
Services

Maintenance
Management

Portals

Experimental
Services

Application Services and

Tools
Provide Common End User Interface Tools
Application generators, test suites, error

identification, application components and

standard utilities.
Common end-user Interface Tools.
E-mail, collaboration tools, information

dashboards, Intranet portals, etc.

78

Example of Development
Tools
Business Process Execution Language,

BPEL, is an executable modeling language.

Through XML it enables code generation.
Traditional Approach
- Hard-coded decision logic
logic
- Developed by IT
analysts
- Maintained by IT
managers
- Managed by IT
-79Dependent upon custom logs
process capture

BPEL Approach
- Externalized decision
- Modeled by business
- Maintained by policy
- Managed by IT
- Automatic logs and

A Few Key SOA Protocols

Universal Description, Discovery, and Integration, UDDI.

Defines the publication and discovery of web service

implementations.
The Web Services Description Language, WSDL, is an
XML-based language that defines Web Services.
SOAP is the Service Oriented Architecture Protocol. It is
a key SOA in which a network node (the client) sends a
request to another node (the server).
The Lightweight Directory Access Protocol, or LDAP is
protocol for querying and modifying directory services.
Extract, Transform, and Load, ETL, is a process of
moving data from a legacy system and loading it into a
SOA application.

80

References
1.

2.
3.
4.
5.
6.
7.
8.

81

Kai Hwang, Geoffery C. Fox and Jack J. Dongarra,

Distributed and Cloud Computing: Clusters, Grids,
Clouds and the Future of Internet,
Distributed Computing.
http://distributedcomputing.info/index.html
Jie Wu, Distributed System Design, CRC Press,
1999.
Distributed Computing, Wikipedia
http://en.wikipedia.org/wiki/Distributed_computing
www.psgtech.edu/yrgcc/attach/GridComputing-an
%20introduction.ppt
www.cse.unr.edu/~mgunes/cpe401/cpe401sp12/lect1
5_cloud.ppt
csnotes.upm.edu.my/kelasmaya/web.nsf/.../
$FILE/Distributed%20Computing.ppt
www.strassmann.com/pubs/gmu/2007-11-slides.ppt

7/22/16

Other presentations
http://www.slideshare.net/drgst/presentations

82

7/22/16

Thank You

Questions and
Comments?

83

7/22/16