Scribd
Upload
37 views

CS4513 Distributed Computer Systems

This document discusses distributed computer systems. It begins with an introduction and definition of distributed systems as a collection of independent computers that appear as a single system to users. It then covers topics like the rise of distributed systems, examples, transparency, and challenges like scalability. It discusses techniques for scaling like hiding communication latency, distribution, and replication. It also covers software concepts in distributed systems like distributed operating systems, network operating systems, and middleware. Finally, it discusses client-server models and multitier architectures.

Uploaded by

Shahnaz Shakir
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
37 views

CS4513 Distributed Computer Systems

This document discusses distributed computer systems. It begins with an introduction and definition of distributed systems as a collection of independent computers that appear as a single system to users. It then covers topics like the rise of distributed systems, examples, transparency, and challenges like scalability. It discusses techniques for scaling like hiding communication latency, distribution, and replication. It also covers software concepts in distributed systems like distributed operating systems, network operating systems, and middleware. Finally, it discusses client-server models and multitier architectures.

Uploaded by

Shahnaz Shakir
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 23

CS4513

Distributed Computer
Systems

Introduction
Outline

• Overview
• Goals
• Software
• Client Server
The Rise of Distributed Systems

• Computer hardware prices falling, power increasing


– If cars the same, Rolls Royce would cost 1 dollar and
get 1 billion miles per gallon (with 200 page manual to
open the door)
• Network connectivity increasing
– Everyone is connected with fat pipes
• It is easy to connect hardware together
• Definition: a distributed system is
– A collection of independent computers that appears
to its users as a single coherent system.
Definition of a Distributed System

Examples:
-The Web
-Processor Pool
-Airline
Reservation

A distributed system organized as middleware.


Note that the middleware layer extends over multiple machines.
Users can interact with the system in a consistent way, regardless
of where the interaction takes place.
Note: Middleware may be “part” of application in practice.
Transparency in a Distributed System
Transparency Description

Hide differences in data representation and how a resource is


Access
accessed

Location Hide where a resource is located

Migration Hide that a resource may move to another location

Hide that a resource may be moved to another location while


Relocation
in use

Hide that a resource may be shared by several competitive


Replication
users

Hide that a resource may be shared by several competitive


Concurrency
users

Failure Hide the failure and recovery of a resource

Persistence Hide whether a (software) resource is in memory or on disk

Different forms of transparency in a distributed system.


Scalability Problems
• As distributed systems grow, centralized solutions
are limited
– Consider LAN name resolution vs. WAN

Concept Example
Centralized services A single server for all users

Centralized data A single on-line telephone book


Doing routing based on complete
Centralized algorithms
information

• Sometimes, hard to avoid (consider a bank)


• Need to collect information in distributed fashion
and distributed in a distributed fashion
• Challenges:
– geography, ownership domains, time synchronization
Scaling Techniques: Hiding
Communication Latency
• Especially important for interactive applications
• If possible, do asynchronous communication
- Not always possible when client has nothing to do

• Instead, can hide latencies


Scaling Techniques: Distribution

1.5

Example: DNS name space into zones


(nl.vu.cs.fluit – z1 gives address of vu gives
address of cs)
Scaling Techniques: Replication
• Copy of information to increase availability
and decrease centralized load
– Example: P2P networks (Gnutella +)
distribute copies uniformly or in proportion
to use
– Example: CDNs (akamai)
– Example: Caching is a replication decision
made by client
• Issue: Consistency of replicated
information
– Example: Web Browser cache
Outline

• Overview (done)
• Goals (done)
• Software 
• Client Server
Software Concepts
System Description Main Goal

Tightly-coupled operating system for multi- Hide and manage


DOS
processors and homogeneous multicomputers hardware resources
Loosely-coupled operating system for
Offer local services
NOS heterogeneous multicomputers (LAN and
to remote clients
WAN)
Additional layer atop of NOS implementing Provide distribution
Middleware
general-purpose services transparency

• DOS (Distributed Operating Systems)


• NOS (Network Operating Systems)
• Middleware
Uniprocessor Operating Systems

• Separating applications from operating


system code through a microkernel
– Can extend to multiple computers
Distributed Operating Systems

• But no longer have shared memory


– Provide message passing
– Can try to provide distributed shared memory
• But tough to get acceptable performance
Network Operating System

• OSes can be different (Windows or Linux)


• Typical services: rlogin, rcp
– Fairly primitive way to share files
Network Operating System

• Can have one computer provide files transparently for others


(NFS)
– (try a “df” on the WPI hosts to see. Similar to a “mount network
drive” in Windows)
Network Operating System

• Different clients may mount the servers in different places


• Inconsistencies in view make NOSes harder, in general for
users than DOSes.
– But easier to scale by adding computers
Positioning Middleware
• Network OS not transparent. Distributed OS not
independent of computers.
– Middleware can help

• Much middleware built in-house to help use networked


operating systems (distributed transactions, better comm,
RPC)
• Unfortunately, many different standards
Outline

• Overview (done)
• Goals (done)
• Software (done)
• Client Server 
Clients and Servers
• Thus far, have not talked about organization of
processes
– Again, many choices but most agree upon is client-server

• If can do so without connection, quite simple


• If underlying connection is unreliable, not trivial
• Resend. What if receive twice?
• Use TCP for reliable connection (most Inet apps)
• Not always appropriate for high-speed LAN connection or
interactive applications
Client-Server Implementation Levels

• Example of an Internet search engine


– UI on client
– Processing can be on client or server
– Data level is server, keeps consistency
Multitiered Architectures

• Thin client (a) to Fat client (e)


– (d) and (e) popular for NOS environments
Multitiered Architectures: 3 tiers

• Server may act as a client


– Example would be transaction monitor across multiple databases
Modern Architectures: Horizontal

• Rather than vertical, distribute servers across nodes


– Example of Web server “farm” for load balancing
– Clients, too (peer-to-peer systems)

You might also like