Definition of a Distributed System (1)

A distributed system is:

Introduction
Chapter 1

A collection of independent computers that appears to its users as a single coherent system.

Definition of a Distributed System (2)

Transparency in a Distributed System

Transparency Access Location Migration Relocation Description Hide differences in data representation and how a resource is accessed Hide where a resource is located Hide that a resource may move to another location Hide that a resource may be moved to another location while in use Hide that a resource may be shared by several competitive users Hide that a resource may be shared by several competitive users Hide the failure and recovery of a resource Hide whether a (software) resource is in memory or on disk

1.1

Replication Concurrency Failure Persistence

A distributed system organized as middleware. Note that the middleware layer extends over multiple machines.

Different forms of transparency in a distributed system.

Scalability Problems
Concept Centralized services Centralized data Centralized algorithms Example A single server for all users A single on-line telephone book Doing routing based on complete information

Scaling Techniques (1)

1.4

Examples of scalability limitations.

The difference between letting: a) a server or b) a client check forms as they are being filled

Scaling Techniques (2)

Hardware Concepts

1.6 1.5

An example of dividing the DNS name space into zones.

Different basic organizations and memories in distributed computer systems

Multiprocessors (1)

Multiprocessors (2)

1.7 1.8

A bus-based multiprocessor.

a) A crossbar switch b) An omega switching network

Homogeneous Multicomputer Systems

System DOS

Software Concepts
Description Tightly-coupled operating system for multiprocessors and homogeneous multicomputers Loosely-coupled operating system for heterogeneous multicomputers (LAN and WAN) Additional layer atop of NOS implementing general-purpose services Main Goal Hide and manage hardware resources Offer local services to remote clients Provide distribution transparency

1-9

NOS

Middleware

a) Grid b) Hypercube

An overview of DOS (Distributed Operating Systems) NOS (Network Operating Systems) Middleware

Uniprocessor Operating Systems

Multiprocessor Operating Systems (1)

monitor Counter { private: int count = 0; public: int value() { return count;} void incr () { count = count + 1;} void decr() { count = count 1;} }

1.11

Separating applications from operating system code through a microkernel.

A monitor to protect an integer against concurrent access.

Multiprocessor Operating Systems (2)

monitor Counter { private: int count = 0; int blocked_procs = 0; condition unblocked; public: int value () { return count;} void incr () { if (blocked_procs == 0) count = count + 1; else signal (unblocked); } } } void decr() { if (count ==0) { blocked_procs = blocked_procs + 1; wait (unblocked); blocked_procs = blocked_procs 1; } else count = count 1;

Multicomputer Operating Systems (1)

1.14

A monitor to protect an integer against concurrent access, but blocking a process.

General structure of a multicomputer operating system

Multicomputer Operating Systems (2)

Multicomputer Operating Systems (3)

Synchronization point Send buffer Yes No No No Reliable comm. guaranteed? Not necessary Not necessary Necessary Necessary

1.15

Block sender until buffer not full Block sender until message sent Block sender until message received Block sender until message delivered

Relation between blocking, buffering, and reliable communications. Alternatives for blocking and buffering in message passing.

Distributed Shared Memory Systems (1)

a) Pages of address space distributed among four machines Situation after CPU 1 references page 10 Situation if page 10 is read only and replication is used

Distributed Shared Memory Systems (2)

1.18

b)

c)

False sharing of a page between two independent processes.

Network Operating System (1)

Network Operating System (2)

1-19

1-20

General structure of a network operating system.

Two clients and a server in a network operating system.

Network Operating System (3)

Positioning Middleware

1-22 1.21

Different clients may mount the servers in different places.

General structure of a distributed system as middleware.

Middleware and Openness

Comparison between Systems

Item Degree of transparency Same OS on all nodes Distributed OS Multiproc. Very High Yes 1 Shared memory Global, central No Closed Multicomp. High Yes N Messages Global, distributed Moderately Closed Network OS Low No N Files Per node Yes Open Middlewarebased OS High No N Model specific Per node Varies Open

1.23

Number of copies of OS Basis for communication Resource management Scalability Openness

In an open middleware-based distributed system, the protocols used by each middleware layer should be the same, as well as the interfaces they offer to applications.

A comparison between multiprocessor operating systems, multicomputer operating systems, network operating systems, and middleware based distributed systems.

Clients and Servers

1.25

An Example Client and Server (1)

General interaction between a client and a server. The header.h file used by the client and server.

An Example Client and Server (2)

An Example Client and Server (3)

1-27 b

A sample server. A client using the server to copy a file.

Processing Level

Multitiered Architectures (1)

1-28

1-29

The general organization of an Internet search engine into three different layers

Alternative client-server organizations (a) (e).

Multitiered Architectures (2)

Modern Architectures

1-31 1-30

An example of a server acting as a client.

An example of horizontal distribution of a Web service.