1 Distributed Systems Architectures Chapter 2. 2 Course/Slides Credits Note: all course presentations are based on those developed by Andrew S. Tanenbaum.

Slides:



Advertisements
Similar presentations
CS-495 Distributed Systems Fabián E. Bustamante, Winter 2004 Introduction Distributed Systems Goals of Distributed Systems Hardware and Software Concepts.
Advertisements

Architectures. Architectural Styles (1)  Considering the logical organization of distributed systems into software components, also referred to as software.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
1 Distributed Systems Alexis Delis Monday 6:00-9:00 Spring 2002
Definition of a Distributed System (1) A distributed system is: A collection of independent computers that appears to its users as a single coherent system.
Distributed Systems1 Chapter 2: Concepts and Architectures CPU Memory I/O Disk(s) Traditional Computer Architecture.
CS 620 Advanced Operating Systems Lecture 4 – Distributed System Architectures Professor Timothy Arndt BU 331.
Introduction Chapter 1.
REK’s adaptation of Prof. Claypool’s adaptation of
Chapter 1  Introduction 1 Introduction Chapter 1.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Based on last years lecture notes, used by Juha Takkinen.
CS4513 Distributed Computer Systems Introduction (Ch 1: , )
SKR 4401 Distributed Systems
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Introducing … Distributed Systems.
1 Introduction Chapter 1. 2 Definition of a Distributed System (1) A distributed system is: A collection of independent computers that appears to its.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Computer Science Lecture 1, page 1 CS677: Distributed OS Distributed Operating Systems Spring 2005 Prashant Shenoy UMass Computer Science
Distributed Systems CS 3850 Soufiane Noureddine Lectures MWF 14:00 – 14:50 (PE207D) Office Hours MW 11:00 – 12:00 (C520)
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Hardware/Software Concepts Tran, Van Hoai Department of Systems & Networking Faculty of Computer Science & Engineering HCMC University of Technology.
Dr. Kalpakis CMSC621 Advanced Operating Systems Introduction.
Massively Distributed Database Systems Spring 2014 Ki-Joune Li Pusan National University.
Introduction Chapter 1. Definition of a Distributed System A distributed system [Tannenbaum & Steen] can be defined as a collection of independent computers.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Chapter 2 ARCHITECTURES.
Advanced Operating Systems Welcome to this course, in Fall Semester Main TextBooks 1- Tanenbaum’s book 2- Chow’s Book 3- Singhal’s Book Other extra.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Chapter 2 ARCHITECTURES.
1 CS 6823 ASU Chapter 2 Architecture.
Architectures of distributed systems Fundamental Models
Distributed Systems COEN 317 Introduction Chapter 1,2,3.
Types of Operating Systems
OS2- Sem ; R. Jalili Introduction Chapter 1.
Kyung Hee University 1/41 Introduction Chapter 1.
DISTRIBUTED COMPUTING Introduction Dr. Yingwu Zhu.
Fall 2007cs4251 Distributed Computing Umar Kalim Dept. of Communication Systems Engineering 19/09/2007.
Introducing … Distributed Systems Paul Barry Muhammed Cinsdikici.
1 Introduction Chapter 1. 2 The Textbook  Andrew S. Tanenbaum & Maarten van Steen, Distributed Systems: Principles and Paradigms, Prentice Hall, 2002.
OS2- Sem1-83; R. Jalili Introduction Chapter 1. OS2- Sem1-83; R. Jalili Definition of a Distributed System (1) A distributed system is: A collection of.
1 Distributed Systems Distributed Web-Based Systems Chapter 12.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
Distributed (Operating) Systems -Architectures- Computer Engineering Department Distributed Systems Course Assoc. Prof. Dr. Ahmet Sayar Kocaeli University.
Distributed Systems: Principles and Paradigms By Andrew S. Tanenbaum and Maarten van Steen.
Definition of a Distributed System (1) A distributed system is: A collection of independent computers that appears to its users as a single coherent system.
Types of Operating Systems 1 Computer Engineering Department Distributed Systems Course Assoc. Prof. Dr. Ahmet Sayar Kocaeli University - Fall 2015.
Introduction Chapter 1. Definition of a Distributed System (1) A distributed system is: A collection of independent computers that appears to its users.
1 Distributed Systems Distributed Object-Based Systems Chapter 10.
第 1 讲 分布式系统概述 §1.1 分布式系统的定义 §1.2 分布式系统分类 §1.3 分布式系统体系结构.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED.
Distributed Computing Systems CSCI 6900/4900. Review Definition & characteristics of distributed systems Distributed system organization Design goals.
TEXT: Distributed Operating systems A. S. Tanenbaum Papers oriented on: 1.OS Structures 2.Shared Memory Systems 3.Advanced Topics in Communications 4.Distributed.
Primitive Concepts of Distributed Systems Chapter 1.
Univ. of TehranDistributed Operating Systems1 Advanced Operating Systems University of Tehran Dept. of EE and Computer Engineering By: Dr. Nasser Yazdani.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Architectural.
Distributed Systems Architecure. Architectures Architectural Styles Software Architectures Architectures versus Middleware Self-management in distributed.
Introduction Chapter 1. Definition of a Distributed System (1) A distributed system is: A collection of independent computers that appears to its users.
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Definition of Distributed System
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
CHAPTER 3 Architectures for Distributed Systems
Advanced Operating Systems
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Introduction Chapter 1.
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
Presentation transcript:

1 Distributed Systems Architectures Chapter 2

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 (1 st & 2 nd editions). hor_tanenbaum/custom/dist_sys_1e/index.html hor_tanenbaum/custom/dist_sys_1e/index.html And additions made by Paul Barry in course CW046-4: Distributed Systems

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.

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

5 Layered vs. Microkernel Architecture

6 Types of Operating Systems SystemDescriptionMain Goal DOS Tightly-coupled operating system for multi- processors and homogeneous multicomputers Hide and manage hardware resources NOS Loosely-coupled operating system for heterogeneous multicomputers (LAN and WAN) Offer local services to remote clients Middleware Additional layer atop of NOS implementing general-purpose services Provide distribution transparency

7 Multicomputer Operating Systems General structure of a multicomputer operating system – all the systems are of the same type: homogeneous 1.14

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

9 Distributed Shared Memory Systems (2) False sharing of a page between 2 independent processes

10 Network Operating System (1) General structure of a network operating system – all the systems are of different types: heterogeneous 1-19

11 Network Operating System (2) Two clients and a server in a network operating system – relatively primitive set of services provided 1-20

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

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.

14 Positioning Middleware General structure of a distributed system as middleware 1-22

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

16 Comparison between the systems Item Distributed OS Network OS Middleware- based OS Multiproc.Multicomp. Degree of transparencyVery HighHighLowHigh Same OS on all nodesYes No Number of copies of OS1NNN Basis for communication Shared memory MessagesFilesModel specific Resource managementGlobal, central Global, distributed Per node ScalabilityNoModeratelyYesVaries OpennessClosed Open

17 Architectural Styles Important styles of architecture for distributed systems: –Layered architectures –Object-based architectures –Data-centered architectures –Event-based architectures

18 Architectural Styles (2) The (a) layered architectural style and …

19 Architectural Styles (3) (b) The object-based architectural style

20 Architectural Styles (4) (a) The event-based architectural style and …

21 Architectural Styles (5) (b) The shared data-space architectural style

22 Centralized Architectures Client/Server Model General interaction between a client and a server

23 Alternatives for blocking and buffering in message passing 1.15

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

25 Application Leveling (1) Traditional three levels of architectural style: 1.User-interface level 2.Processing level 3.Data level

26 Application Leveling (2) The simplified organization of an Internet search engine into three different levels

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.

28 Multi-tiered Architectures (2) Alternative client-server organizations (a)–(e)

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

30 Replicated Web Servers An example of horizontal distribution of a Web service (often also referred to as “clustering”) 1-31

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.

32 Structured Peer-to-Peer Architectures (1) The mapping of data items onto nodes in Chord

33 Structured Peer-to-Peer Architectures (2) (a) The mapping of data items onto nodes in CAN

34 Structured Peer-to-Peer Architectures (3) (b) Splitting a region when a node joins

35 Unstructured Peer-to-Peer Architectures (1) (a) The steps taken by the active thread

36 Unstructured Peer-to-Peer Architectures (2) (b) The steps taken by the passive thread

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

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)]

39 Superpeers A hierarchical organization of nodes into a superpeer network

40 Hybrid Architectures Edge-Server Systems Viewing the Internet as consisting of a collection of edge servers

41 Collaborative Distributed Systems (1) The principal working of BitTorrent [adapted with permission from Pouwelse et al. (2004)]

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.

43 Interceptors Using interceptors to handle remote-object invocations

44 General Approaches to Adaptive Software Three basic approaches to adaptive software: 1.Separation of concerns 2.Computational reflection 3.Component-based design

45 Self-Managing DSs The Feedback Control Model The logical organization of a feedback control system

46 Data collection and information aggregation in Astrolabe Example: Systems Monitoring with Astrolabe

47 Example: Differentiating Replication Strategies in Globule (1) The edge-server model assumed by Globule

48 Example: Differentiating Replication Strategies in Globule (2) The dependency between prediction accuracy and trace length

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.