Distributed Systems

Distributed Systems Failure Handling
Characteristics Checksums (detect corrupted data)
 Concurrency Masking failures

 No global clock
(detected failures can be
 Independent Failures
hidden or made less
Trends in distributed systems severe, i.e.
retransmitting
o Pervasive networking and the
messages that failed to
modern internet
arrive at the
o Mobile and ubiquitous
destination)
computing
o Distributed multimedia systems Tolerating Failures
Focus on resource sharing (Services can inform users of

failed service that way
Challenges the user does not need
Heterogeneity to keep trying, i.e. web
browser cannot
Middleware establish connection to
Mobile code a web server)
Openness Recovery From Failures
Degree to which a new (Roll back mechanisms)

resource-sharing service can be added Redundancy
and be made available for use by a
variety of client programs. (Components can be made
redundant, such as
Security providing multiple
DOS and Security of Mobile routes to a certain
Code destination)
Scalability Quality Service
scalable when it remains to be reliability, security, and

effective even when there is a performance (and adaptability).
significant increase in the number of
resources and users in the system.
controlling the cost of

physical resources,
controlling the performance
loss, preventing software
resources running out,
avoiding performance
bottlenecks.
EAI (Enterprise Application Integration) Pros of Presentation Integration:
Combination of processes, software, • Low risk, low cost

standards • Technology is available and stable
Three models • Easy to accomplish
Presentation Integration Model (User Interface • Quickly implemented
Integration)
• Does not require changes to source or target
systems
• Presentation logic is less compressed compare to

data or functional logic
Cons of Presentation Integration:
• Performance
• Only prolonging the EAI problem in many instances
• Only the data and interaction defined in the legacy

presentation can be accessed
• Most limiting out of the 3 models
• No interconnection between the application and

This model allows the integration of new software data
through the existing presentation of the legacy
software. This is typically used to create a new user
interface but may be used to integrate with other
applications.
Characteristics:
• Simplest form of integration
• Presentation refer to the user interface that

provide access to an application
• Accessing the legacy application through its

existing presentation logic
• Example of technologies – emulators, terminal

application libraries, screen to
object translators
Data Integration Model
Pros for Data Integration Model
• Greater flexibility than presentation integration

model
• Availability of technology
 Allow data to be reused across other

application.
• Inexpensive and proven technology
Cons for Data Integration Model
• Integration is tied to a data model, if a data model

changes, the integration may break
• Does not solve the ultimate method integration

problem, more of a stop gap measure
Data integration model allows the integration of

software through access to the
data that is created, managed, and stored by the

software typically for the
purpose of reusing or synchronizing data across

applications.
Characteristics:
• It goes directly into the database or data structure

of an application
bypassing the presentation and business logic to

create the integration.
• Using tools and data access middleware to access

and integrate information
from database such as batch file transfer, Open

Database Connectivity
(ODBC), Data transformation.
• Allow combination of data from multiple sources

for analysis and decision
making or data extraction from one source and

reformatted into another.
Functional Integration Model (Method level Pros for Functional Integration Model
integration)
• Most robust integration capabilities of all the
models
• Provides true code reuse infrastructure for many

enterprise applications
• Availability of technology and expertise
• Ultimate EAI solution for many enterprises
Cons for Functional Integration Model
• Much more complex and expensive that the other

approaches
• High learning curves for the software
• Takes a lot of time, architecture, and planning
• Enabling technology may not scale to enterprise

This model allows for the integration of software for
class applications or fall
the purpose of invoking existing
short in other ways
functionality form other new or existing applications.
The integration is done • May be difficult to access the business logic of
some applications because
through interfaces to the software.
the source codes may not exist or may have no APIs.
Characteristics:
• Functional integration model integrates at the

business logic level using distributed processing
middleware
Distributed processing middleware is a type of

software that facilitates at the communication of
requests between software components using
defined interfaces or messages.
Why Networked?  Centralized management
Besides classic applications like email, web browsers, Things to consider in CS computing:
and the like, most major applications have some
level of networking built in. The following are just  Basic Network Concepts
some. examples:  Sockets for Servers
 Sockets for Clients
• Text editors like BBEdit save and open files directly  Streams
from FTP servers.  Threads
• IDEs like Eclipse and IntelliJ IDEA communicate
with VCS repositories.
• Word processors like Microsoft Word open files

from URLs.
• Antivirus programs like TrendMicro check for new

virus definitions by
connecting to the vendor's web site every time the

computer is started.
• Music players upload CD track info to CDDB and

download the corresponding track titles.
Why Java?
Java was the first programming language designed

from the ground up with networking in mind. One of
the biggest secrets about Java is that it makes
writing network programs easy. The part of the
program that deals with the network is almost
always the shortest and simplest.
Client Role Server Role

 Presentation Services “Business” Functionalities
User Input and supporting the operation
Showing of Output of the client application
Samples of Clients and Servers
Client Server
Web Browser Web Server/Daemon
Web Browser FTP Server/Daemon
Email Client SMTP Server/Daemon
Email Client POP or IMAP
Server/Daemon
Why use CS Computing
 Improved data sharing

 Integrated services
 Resource sharing
 Data interchangeability and interoperability
 Masked physical data access.
 Location independence of data and processing

Distributed Systems

Uploaded by

Copyright:

Available Formats

Distributed Systems

Uploaded by

Document Information

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

Distributed Systems

Uploaded by

Copyright:

Available Formats

Distributed Systems Failure Handling

Characteristics Checksums (detect corrupted data)

 Concurrency Masking failures

Focus on resource sharing (Services can inform users of

Openness Recovery From Failures

Degree to which a new (Roll back mechanisms)

Scalability Quality Service

scalable when it remains to be reliability, security, and

controlling the cost of

Combination of processes, software, • Low risk, low cost

• Presentation logic is less compressed compare to

Cons of Presentation Integration:

• Only prolonging the EAI problem in many instances

• Only the data and interaction defined in the legacy

• Most limiting out of the 3 models

• No interconnection between the application and

• Simplest form of integration

• Presentation refer to the user interface that

• Accessing the legacy application through its

• Example of technologies – emulators, terminal

• Greater flexibility than presentation integration

 Allow data to be reused across other

• Inexpensive and proven technology

Cons for Data Integration Model

• Integration is tied to a data model, if a data model

• Does not solve the ultimate method integration

Data integration model allows the integration of

data that is created, managed, and stored by the

purpose of reusing or synchronizing data across

• It goes directly into the database or data structure

bypassing the presentation and business logic to

• Using tools and data access middleware to access

from database such as batch file transfer, Open

(ODBC), Data transformation.

• Allow combination of data from multiple sources

making or data extraction from one source and

• Provides true code reuse infrastructure for many

• Availability of technology and expertise

• Ultimate EAI solution for many enterprises

Cons for Functional Integration Model

• Much more complex and expensive that the other

• High learning curves for the software

• Takes a lot of time, architecture, and planning

• Enabling technology may not scale to enterprise

• Functional integration model integrates at the

Distributed processing middleware is a type of

• Word processors like Microsoft Word open files

• Antivirus programs like TrendMicro check for new

connecting to the vendor's web site every time the

• Music players upload CD track info to CDDB and

Java was the first programming language designed

Client Role Server Role

 Improved data sharing

You might also like