distributed systems
DESCRIPTION
Distributed Systems. Architectures Chapter 2. Course/Slides Credits. - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/1.jpg)
1
Distributed Systems
Architectures Chapter 2
![Page 2: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/2.jpg)
2
Course/Slides Credits
Note: all course presentations are based on those developed by Andrew S. Tanenbaum and Maarten van Steen. They accompany their "Distributed Systems: Principles and Paradigms" textbook (1st & 2nd editions).http://www.prenhall.com/divisions/esm/app/author_tanenbaum/custom/dist_sys_1e/index.html
And additions made by Paul Barry in course CW046-4: Distributed Systems
http://glasnost.itcarlow.ie/~barryp/net4.html
![Page 3: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/3.jpg)
3
Modeling Distributed Systems
• When building distributed applications, system builders have often looked to the non-distributed systems world for models to follow (… inspiration?).
• Consequently, distributed systems tend to exhibit certain characteristics that are already familiar to us.
• This applies equally to hardware concepts as it does to software concepts.
![Page 4: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/4.jpg)
4
Uniprocessor Operating Systems
Separating applications from operating system code through a “microkernel” – can provide a good base upon which to build a distributed OS (DOS)
1.11
![Page 5: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/5.jpg)
5
Layered vs. Microkernel Architecture
![Page 6: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/6.jpg)
6
Types of Operating Systems
SystemDescriptionMain Goal
DOSTightly-coupled operating system for multi-processors and homogeneous multicomputers
Hide and manage hardware resources
NOSLoosely-coupled operating system for heterogeneous multicomputers (LAN and WAN)
Offer local services to remote clients
MiddlewareAdditional layer atop of NOS implementing general-purpose services
Provide distribution transparency
![Page 7: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/7.jpg)
7
Multicomputer Operating Systems
General structure of a multicomputer operating system – all the systems are of the same type: homogeneous
1.14
![Page 8: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/8.jpg)
8
Distributed Shared Memory Systems (1)
a) Pages of address space distributed among four machines
b) Situation after CPU 1 references page 10
c) Situation if page 10 is read only and replication is used
![Page 9: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/9.jpg)
9
Distributed Shared Memory Systems (2)
False sharing of a page between 2 independent processes
![Page 10: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/10.jpg)
10
Network Operating System (1)
General structure of a network operating system – all the systems are of different types: heterogeneous
1-19
![Page 11: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/11.jpg)
11
Network Operating System (2)
Two clients and a server in a network operating system – relatively primitive set of services provided
1-20
![Page 12: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/12.jpg)
12
Network Operating System (3)
Different clients may mount the servers in different places – difficult to maintain a consistent “view” of the system
1.21
![Page 13: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/13.jpg)
13
The Best of Both Worlds?• DOS: too inflexible (all systems of the
same type).• NOS: too primitive (lowest common
denominator – too much diversity).• “Middleware” – best possible
compromise?• Middleware = NOS + additional software
layer.
![Page 14: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/14.jpg)
14
Positioning Middleware
General structure of a distributed system as middleware
1-22
![Page 15: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/15.jpg)
15
Middleware and 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. This is a much higher level of abstraction than (for instance) the NOS Socket API.
1.23
![Page 16: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/16.jpg)
16
Comparison between the systems
ItemDistributed OS
Network OS
Middleware-based OS Multiproc.Multicomp
.Degree of
transparencyVery HighHighLowHigh
Same OS on all nodesYesYesNoNo
Number of copies of OS1NNN
Basis for communication
Shared memoryMessagesFilesModel
specificResource
managementGlobal, central
Global, distributedPer nodePer node
ScalabilityNoModeratelyYesVaries
OpennessClosedClosedOpenOpen
![Page 17: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/17.jpg)
17
Architectural Styles
• Important styles of architecture for distributed systems:
– Layered architectures– Object-based architectures– Data-centered architectures– Event-based architectures
![Page 18: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/18.jpg)
18
Architectural Styles (2)
The (a) layered architectural style and …
![Page 19: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/19.jpg)
19
Architectural Styles (3)
(b) The object-based architectural style
![Page 20: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/20.jpg)
20
Architectural Styles (4)
(a) The event-based architectural style and …
![Page 21: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/21.jpg)
21
Architectural Styles (5)
(b) The shared data-space architectural style
![Page 22: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/22.jpg)
22
Centralized ArchitecturesClient/Server Model
General interaction between a client and a server
![Page 23: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/23.jpg)
23
Alternatives for blocking and buffering in message passing
1.15
![Page 24: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/24.jpg)
24
Relation between blocking, buffering, and reliable communications
Synchronization pointSender buffer
Reliable communication guaranteed?
Block sender until buffer not fullYesNot necessarily
Block sender until message sentNoNot necessarily
Block sender until message receivedNoNecessary
Block sender until message deliveredNoNecessary
![Page 25: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/25.jpg)
25
Application Leveling (1)
• Traditional three levels of architectural style:
1. User-interface level2. Processing level3. Data level
![Page 26: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/26.jpg)
26
Application Leveling (2)
The simplified organization of an Internet search engine into three different levels
![Page 27: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/27.jpg)
27
Multi-tiered Architectures (1)
• The simplest organization is to have only two types of machines:
1. A client machine containing only the programs implementing (part of) the user-interface level.
2. A server machine containing the rest, the programs implementing the processing and data levels.
![Page 28: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/28.jpg)
28
Multi-tiered Architectures (2)
Alternative client-server organizations (a)–(e)
![Page 29: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/29.jpg)
29
Multi-tiered Architectures (3)
An example of a server acting as a client – this is a very common vertical distribution model for distributed systems
![Page 30: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/30.jpg)
30
Replicated Web Servers
An example of horizontal distribution of a Web service (often also referred to as “clustering”)
1-31
![Page 31: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/31.jpg)
31
Decentralized Architectures
• Three types of Peer-to-Peer (P2P) systems:1. Structured P2P: nodes are organized
following a specific distributed data structure.
2. Unstructured P2P: nodes have randomly selected neighbors.
3. Hybrid P2P: some nodes are appointed special functions in a well-organized fashion.
![Page 32: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/32.jpg)
32
Structured Peer-to-Peer Architectures (1)
The mapping of data items onto nodes in Chord
![Page 33: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/33.jpg)
33
Structured Peer-to-Peer Architectures (2)
(a) The mapping of data items onto nodes in CAN
![Page 34: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/34.jpg)
34
Structured Peer-to-Peer Architectures (3)
(b) Splitting a region when a node joins
![Page 35: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/35.jpg)
35
Unstructured Peer-to-Peer Architectures (1)
(a) The steps taken by the active thread
![Page 36: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/36.jpg)
36
Unstructured Peer-to-Peer Architectures (2)
(b) The steps taken by the passive thread
![Page 37: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/37.jpg)
37
Topology Management of Overlay Networks (1)
A two-layered approach for constructing and maintaining specific overlay topologies using techniques from unstructured peer-to-peer systems
![Page 38: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/38.jpg)
38
Topology Management of Overlay Networks (2)
Generating a specific overlay network using a two-layered unstructured peer-to-peer system [adapted with permission from Jelasity and Babaoglu (2005)]
![Page 39: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/39.jpg)
39
Superpeers
A hierarchical organization of nodes into a superpeer network
![Page 40: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/40.jpg)
40
Hybrid ArchitecturesEdge-Server Systems
Viewing the Internet as consisting of a collection of edge servers
![Page 41: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/41.jpg)
41
Collaborative Distributed Systems (1)
The principal working of BitTorrent [adapted with permission from Pouwelse et al. (2004)]
![Page 42: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/42.jpg)
42
Collaborative Distributed Systems (2)
• Components of Globule collaborative content distribution network:
– A component that can redirect client requests to other servers.
– A component for analyzing access patterns.– A component for managing the replication
of Web pages.
![Page 43: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/43.jpg)
43
Interceptors
Using interceptors to handle remote-object invocations
![Page 44: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/44.jpg)
44
General Approaches to Adaptive Software
• Three basic approaches to adaptive software:
1. Separation of concerns2. Computational reflection3. Component-based design
![Page 45: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/45.jpg)
45
Self-Managing DSs The Feedback Control Model
The logical organization of a feedback control system
![Page 46: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/46.jpg)
46 Data collection and information aggregation in Astrolabe
Example: Systems Monitoring with Astrolabe
![Page 47: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/47.jpg)
47
Example: Differentiating Replication Strategies in Globule (1)
The edge-server model assumed by Globule
![Page 48: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/48.jpg)
48
Example: Differentiating Replication Strategies in Globule (2)
The dependency between prediction accuracy and trace length
![Page 49: Distributed Systems](https://reader036.vdocuments.us/reader036/viewer/2022081602/56815e2d550346895dcc86e8/html5/thumbnails/49.jpg)
49
Example: Automatic Component Repair Management in Jade
• Steps required in a repair procedure:– Terminate every binding between a
component on a non-faulty node, and a component on the node that just failed.
– Request the node manager to start and add a new node to the domain.
– Configure the new node with exactly the same components as those on crashed node.
– Re-establish all the bindings that were previously terminated.