Scribd Logo
Upload

Welcome to Scribd!

  • 356 views

    Distributed Systems Characterization and Design

    Uploaded by

    khoadpla
    This document discusses distributed systems, providing examples like local area networks, database management systems, and the internet. It outlines common characteristics such as heterogeneity, security, and failure handling. The basic design issues covered include naming, communication, software structure, and system architectures like client-server and peer-to-peer.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Distributed Systems Characterization and Design

    Uploaded by

    khoadpla
    356 views35 pages
    This document discusses distributed systems, providing examples like local area networks, database management systems, and the internet. It outlines common characteristics such as heterogeneity, security, and failure handling. The basic design issues covered include naming, communication, software structure, and system architectures like client-server and peer-to-peer.

    Original Description:

    Distributed Systems Characterization and Design

    Original Title

    Distributed Systems Characterization and Design

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses distributed systems, providing examples like local area networks, database management systems, and the internet. It outlines common characteristics such as heterogeneity, security, and failure handling. The basic design issues covered include naming, communication, software structure, and system architectures like client-server and peer-to-peer.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    356 views35 pages

    Distributed Systems Characterization and Design

    Uploaded by

    khoadpla
    This document discusses distributed systems, providing examples like local area networks, database management systems, and the internet. It outlines common characteristics such as heterogeneity, security, and failure handling. The basic design issues covered include naming, communication, software structure, and system architectures like client-server and peer-to-peer.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    You are on page 1of 35

    1DT057 DISTRIBUTED INFORMATION SYSTEM

    Distributed Systems Characterization and Design

    OUTLINE

    1. What is a Distributed System 2. Examples of Distributed Systems 3. Common Characteristics 4. Basic Design Issues 5. Summary

    1. DISTRIBUTED SYSTEM TYPES

    Control

    Fully Distributed

    Autonomous fully cooperative Autonomous transaction based Master-slave Homog. Homog. general special purpose purpose Heterog. Heterog. special general purpose purpose

    Local data, local directory Not fully replicated master directory Fully replicated

    Processors
    3

    1. WHAT IS A DISTRIBUTED SYSTEM?

    Definition: A distributed system is one in which components located at networked computers communicate and coordinate their actions only by passing messages. This definition leads to the following characteristics of distributed systems: Concurrency of components Lack of a global clock Independent failures of components

    1.1 CENTRALIZED SYSTEM CHARACTERISTICS


    One component with non-autonomous parts Component shared by users all the time All resources accessible

    Software runs in a single process


    Single point of control

    Single point of failure


    5

    1.2 DISTRIBUTED SYSTEM CHARACTERISTICS


    Multiple autonomous components Components are not shared by all users Resources may not be accessible Software runs in concurrent processes on different processors Multiple points of control Multiple points of failure
    6

    2. EXAMPLES OF DISTRIBUTED SYSTEMS


    Local Area Network and Intranet


    Database Management System Automatic Teller Machine Network Internet/World-Wide Web Mobile and Ubiquitous Computing

    2.1 LOCAL AREA NETWORK


    em ail s erv er print and other serv ers Local area network

    Desktop computers

    Web serv er

    em ail s erv er File serv er print other s erv ers the res t of the Internet router/firewall
    8

    2.2 DATABASE MANAGEMENT SYSTEM

    2.3 AUTOMATIC TELLER MACHINE NETWORK

    10

    2.4 INTERNET
    intranet % % ISP % %

    backbone

    satellite link desktop computer: server: network link: 11

    2.4.1 WORLD-WIDE-WEB

    12

    2.4.2 WEB SERVERS AND WEB BROWSERS


    www.google.com Web servers www.uu.se Internet http://www.google.comlsearch?q=lyu

    Browsers

    http://www.uu.se/
    www.w3c.org File system of www.w3c.org http://www.w3c.org/Protocols/Activity.html Protocols

    Activity.html
    13

    2.5 MOBILE AND UBIQUITOUS COMPUTING


    Internet

    Host intranet

    Wireless LAN

    GSM/GPRS gateway

    Home intranet

    Printer Camera

    Mobile phone Laptop

    Host site
    14

    3. COMMON CHARACTERISTICS

    What are we trying to achieve when we construct a distributed system? Certain common characteristics can be used to assess distributed systems Heterogeneity Openness Security Scalability Failure Handling Concurrency Transparency
    15

    3.1 HETEROGENEITY

    Variety and differences in Networks Computer hardware Operating systems Programming languages Implementations by different developers Middleware as software layers to provide a programming abstraction as well as masking the heterogeneity of the underlying networks, hardware, OS, and programming languages (e.g., CORBA). Mobile Code to refer to code that can be sent from one computer to another and run at the destination (e.g., Java applets and Java virtual machine).
    16

    3.2 OPENNESS
    Openness is concerned with extensions and improvements of distributed systems. Detailed interfaces of components need to be published. New components have to be integrated with existing components. Differences in data representation of interface types on different processors (of different vendors) have to be resolved.

    17

    3.3 SECURITY

    In a distributed system, clients send requests to access data managed by servers, resources in the networks:

    Doctors requesting records from hospitals Users purchase products through electronic commerce Concealing the contents of messages: security and privacy Identifying a remote user or other agent correctly (authentication) Denial of service attack Security of mobile code

    Security is required for:


    New challenges:

    18

    3.4 SCALABILITY

    Adaptation of distributed systems to

    accommodate more users respond faster (this is the hard one)

    Usually done by adding more and/or faster processors.

    Components should not need to be changed when scale of a system increases.


    Design components to be scalable!

    19

    3.5 FAILURE HANDLING (FAULT TOLERANCE)


    Hardware, software and networks fail! Distributed systems must maintain availability even at low levels of hardware/software/network reliability. Fault tolerance is achieved by
    recovery redundancy

    20

    3.6 CONCURRENCY
    Components in distributed systems are executed in concurrent processes. Components access and update shared resources (e.g. variables, databases, device drivers). Integrity of the system may be violated if concurrent updates are not coordinated.

    Lost updates Inconsistent analysis

    21

    3.7 TRANSPARENCY

    Distributed systems should be perceived by users and application programmers as a whole rather than as a collection of cooperating components. Transparency has different aspects.

    These represent various properties that distributed systems should have.

    22

    4. BASIC DESIGN ISSUES


    General

    software engineering principles include rigor and formality, separation of concerns, modularity, abstraction, anticipation of change, Specific issues for distributed systems:

    Naming Communication Software structure System architecture Workload allocation Consistency maintenance
    31

    4.1 NAMING

    A name is resolved when translated into an interpretable form for resource/object reference.
    Communication identifier (IP address + port number) Name resolution involves several translation steps

    Design considerations
    Choice of name space for each resource type Name service to resolve resource names to comm. id.

    Name services include naming context resolution, hierarchical structure, resource protection
    32

    4.2 COMMUNICATION
    Separated components communicate with sending processes and receiving processes for data transfer and synchronization. Message passing: send and receive primitives

    synchronous or blocking asynchronous or non-blocking Abstractions defined: channels, sockets, ports.


    Communication patterns: client-server communication (e.g., RPC, function shipping) and group multicast

    33

    4.3 SOFTWARE STRUCTURE

    Layers in centralized computer systems:

    Applications

    Middleware
    Operating system

    Computer and Network Hardware

    34

    4.3 SOFTWARE STRUCTURE

    Layers and dependencies in distributed systems: Applications Open services

    Distributed programming support Open system kernel services

    Computer and network hardware


    35

    4.4 SYSTEM ARCHITECTURES


    Client-Server Peer-to-Peer Services provided by multiple servers Proxy servers and caches Mobile code and mobile agents Network computers Thin clients and mobile devices

    36

    4.4.1 CLIENTS INVOKE INDIVIDUAL SERVERS

    Client

    inv ocation res ult

    inv ocation res ult

    Serv er

    Serv er

    Client Key : Proc es s: Computer:

    37

    4.4.2 PEER-TO-PEER SYSTEMS Peer 2


    Peer 1 Application Sharable objects Peer 3 Application Application

    Peer 4 Application Peers 5 .... N

    38

    4.4.3 A SERVICE BY MULTIPLE SERVERS


    Serv ic e

    Serv er Client

    Serv er

    Client Serv er
    39

    4.4.4 WEB PROXY SERVER

    Client Prox y serv er

    Web serv er

    Client

    Web serv er

    40

    4.4.5 WEB APPLETS


    a) client reques t results in the downloading of applet code

    Client Applet code b) client interacts with the applet

    Web serv er

    Client

    Applet

    Web serv er
    41

    4.4.6 THIN CLIENTS AND COMPUTE SERVERS


    Compute server

    Network computer or PC

    Thin Client

    network

    Application Process

    42

    5. SUMMARY
    Definitions of distributed systems and comparisons to centralized systems. The characteristics of distributed systems. The eight forms of transparency. The basic design issues. Read Chapter 1 and Chapter 2 of the textbook.

    43

    You might also like