Escolar Documentos
Profissional Documentos
Cultura Documentos
Unit 1 -INTRODUCTION
Unit 1
3/30/2019 UNIT -1 DC 2
Introduction-Networks
3/30/2019 UNIT -1 DC 3
Introduction
3/30/2019 UNIT -1 DC 4
Examples of Distributed Systems
3/30/2019 UNIT -1 DC 5
Figure 1.1
A typical portion of the Internet
intranet %
%
% ISP
backbone
satellite link
desktop computer:
server:
network link:
3/30/2019 UNIT -1 DC 6
Examples of Distributed Systems
3/30/2019 UNIT -1 DC 7
Figure 1.2
A typical intranet
Loc al area
Web server netw ork
email s erv er
print
File s erv er
other s erv ers
the res t of
the Internet
router/firew all
3/30/2019 UNIT -1 DC 8
Examples of Distributed Systems
3/30/2019 UNIT -1 DC 9
Examples of Distributed Systems
3/30/2019 UNIT -1 DC 10
Figure 1.3
Portable and handheld devices in a distributed system
Internet
Mobile
phone
Printer Laptop
Camera Host site
3/30/2019 UNIT -1 DC 11
Resource Sharing
3/30/2019 UNIT -1 DC 13
Resource Sharing
3/30/2019 UNIT -1 DC 14
The World Wide Web (WWW)
3/30/2019 UNIT -1 DC 15
The World Wide Web (WWW)
3/30/2019 UNIT -1 DC 16
The World Wide Web (WWW)
URL (continued):
o ftp://ftp.twsu.edu/ (File Transfer Protocol)
o telnet://kirk.cs.twsu.edu (log into a computer)
o mailto:chang@cs.twsu.edu (identify a user's email
address)
HTTP (HyperText Transfer Protocol) defines a standard
rule by which browsers and any other types of client
interact with web servers. Main features:
o Request-reply interaction
o Content types may or may not be handled by browser -
using plug-in or external helper
3/30/2019 UNIT -1 DC 17
The World Wide Web (WWW)
HTTP (continued):
o One resource per request - Several requests can be
made concurrently.
o Simple access control
o Services and dynamic pages
- form - Common Gateway Interface program on
server (Perl)
- JavaScript (download from server and run on local
computer)
- Applet (download from server and run on local
computer)
3/30/2019 UNIT -1 DC 18
Figure 1.4
Web servers and web browsers
http://www.google.comlsearch?q=kindberg
www.google.com
www.cdk3.net Internet
http://www.cdk3.net/
www.w3c.org
Activity.html
3/30/2019 UNIT -1 DC 19
The World Wide Web (WWW)
• Openness
Key interfaces are published.
It is based on a uniform communication mechanism and
published interfaces for access to shared resources.
It can be constructed from heterogeneous hardware and
software.
• Security
For private or sensitive information - commercial secret
Encryption provides protection of shared resources, keeps
sensitive information secret when transmitted.
Problems: denial of service attacks, security of mobile
code
3/30/2019 UNIT -1 DC 22
Challenges
• Scalability
A scalable system remains effective when there is a
significant increase in the number of resources and users.
Controlling the cost of physical resources - servers and
users
Controlling the performance loss - DNS hierarchic
structures scale better than linear structures and save time
for access structured data.
Preventing software resources running out - Internet 32 bit
addresses run out soon. 128 bit one gives extra space in
messages.
Avoiding performance bottlenecks - DNS name table was
kept in a single master file partitioning between servers.
3/30/2019 UNIT -1 DC 23
Figure 1.5
Computers in the Internet
3/30/2019 UNIT -1 DC 24
Figure 1.6
Computers vs. Web servers in the Internet
3/30/2019 UNIT -1 DC 25
Challenges
• Failure handling
Fail independently - Dependent components should know
and deal with the fails.
Detecting failures
Masking failures - Failures are hidden or made less sever.
Messages could be retransmitted. Files can be duplicated
on different place.
Tolerating failures
Recovery from failures
3/30/2019 UNIT -1 DC 26
Challenges
3/30/2019 UNIT -1 DC 27
Challenges
• Concurrency
Multiple users make requests on same resource (read,
write, update).
Each resource must be safe in a concurrent environment.
• Transparency
To make certain aspects of distributed system invisible to
the application programmer so that they need only be
concerned with the design of their particular application.
The implication of transparency is a major influence on the
design of the system software.
8 forms of transparency - Access, Location, Concurrency,
Replication, Failure, Mobility, Performance, Scaling.
Network transparency – Access and Location
3/30/2019 UNIT -1 DC 28
Figure 1.7
Transparencies
Access transparency: enables local and remote resources to be accessed using identical
operations.
Location transparency: enables resources to be accessed without knowledge of their
location.
Concurrency transparency: enables several processes to operate concurrently using shared
resources without interference between them.
Replication transparency: enables multiple instances of resources to be used to increase
reliability and performance without knowledge of the replicas by users or application
programmers.
Failure transparency: enables the concealment of faults, allowing users and application
programs to complete their tasks despite the failure of hardware or software components.
Mobility transparency: allows the movement of resources and clients within a system
without affecting the operation of users or programs.
Performance transparency: allows the system to be reconfigured to improve performance as
loads vary.
Scaling transparency: allows the system and applications to expand in scale without change
to the system structure or the application algorithms.
3/30/2019 UNIT -1 DC 29