SlideShare una empresa de Scribd logo
1 de 32
CS4513
Distributed Computer
       Systems

       Introduction
   (Ch 1: 1.1-1.2, 1.4-1.5)
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
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)
Example: The Web
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: 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
Multicomputer Operating Systems




•   But no longer have shared memory
     – Can try to provide distributed shared memory
        • Tough, coming up
    – Can provide message passing
Multicomputer Operating Systems




    (optional)                                        (optional)




•    Message passing primitives vary widely between systems
      – Example: consider buffering and synchronization
Multicomputer Operating Systems

                                                         Reliable comm.
    Synchronization point                  Send buffer
                                                         guaranteed?
    Block sender until buffer not full     Yes           Not necessary

    Block sender until message sent        No            Not necessary

    Block sender until message received    No            Necessary

    Block sender until message delivered   No            Necessary


•     Relation between blocking, buffering, and reliable
      communications.
•     These issues make synchronization harder. It was easier when
      we had shared memory.
       – So … distributed shared memory
Distributed Shared Memory Systems

a)    Pages of address
      space distributed
      among four
      machines

c)    Situation after
      CPU 1 references
      page 10

e)    Situation if page
      10 is read only
      and replication is
      used
Distributed Shared Memory Systems
    •   Issue: how large should page sizes be? What are the
        tradeoffs?




•   Overall, DSM systems have struggled to provide efficiency and
    convenience (and been around 15 years)
     – For higher-performance, typically still do message passing
        – Likely will remain that way
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 computers.
    – Middleware can help




• Much middleware built in-house to help use networked
operating systems         (distributed transactions, better
comm, RPC)
     • Unfortunately, many different standards
Middleware and Openness




                           1.23




•     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.
     – If different, compatibility issues
     – If incomplete, then users build their own or use lower-layer
       services (frowned upon)
Comparison between Systems

                          Distributed OS                          Network    Middleware-
Item
                          Multiproc.        Multicomp.            OS         based OS

Degree of transparency    Very High         High                  Low        High
Same OS on all nodes      Yes               Yes                   No         No
Number of copies of OS    1                 N                     N          N
Basis for communication   Shared memory     Messages              Files      Model specific
Resource management       Global, central   Global, distributed   Per node   Per node
Scalability               No                Moderately            Yes        Varies
Openness                  Closed            Closed                Open       Open



•   DOS most transparent, but closed and only moderately
    scalable
•   NOS not so transparent, but open and scalable
•   Middleware provides a bit more transparency than NOS
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 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 (apps on Internet)
     •   Not always appropriate for high-speed LAN connection
         (4513)
Example Client and Server: Header




•   Used by both the client and server.
Example Client and Server: Server
Example Client and Server: Client




• One issue, is how to clearly differentiate
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)

Más contenido relacionado

La actualidad más candente

Apos week 1 4
Apos week 1   4Apos week 1   4
Apos week 1 4
alixafar
 
Chapter 1 characterisation of distributed systems
Chapter 1 characterisation of distributed systemsChapter 1 characterisation of distributed systems
Chapter 1 characterisation of distributed systems
AbDul ThaYyal
 
Chapter 8 distributed file systems
Chapter 8 distributed file systemsChapter 8 distributed file systems
Chapter 8 distributed file systems
AbDul ThaYyal
 
Characteristics of a network operating system
Characteristics of a network operating systemCharacteristics of a network operating system
Characteristics of a network operating system
Ron McGary
 
Chapter 1 -_characterization_of_distributed_systems
Chapter 1 -_characterization_of_distributed_systemsChapter 1 -_characterization_of_distributed_systems
Chapter 1 -_characterization_of_distributed_systems
Francelyno Murela
 

La actualidad más candente (20)

Message Passing, Remote Procedure Calls and Distributed Shared Memory as Com...
Message Passing, Remote Procedure Calls and  Distributed Shared Memory as Com...Message Passing, Remote Procedure Calls and  Distributed Shared Memory as Com...
Message Passing, Remote Procedure Calls and Distributed Shared Memory as Com...
 
Apos week 1 4
Apos week 1   4Apos week 1   4
Apos week 1 4
 
Chapter 1 characterisation of distributed systems
Chapter 1 characterisation of distributed systemsChapter 1 characterisation of distributed systems
Chapter 1 characterisation of distributed systems
 
Distributed computing
Distributed computingDistributed computing
Distributed computing
 
Chapter 8 distributed file systems
Chapter 8 distributed file systemsChapter 8 distributed file systems
Chapter 8 distributed file systems
 
1.intro. to distributed system
1.intro. to distributed system1.intro. to distributed system
1.intro. to distributed system
 
CS9222 ADVANCED OPERATING SYSTEMS
CS9222 ADVANCED OPERATING SYSTEMSCS9222 ADVANCED OPERATING SYSTEMS
CS9222 ADVANCED OPERATING SYSTEMS
 
Distributed operating system
Distributed operating systemDistributed operating system
Distributed operating system
 
Distributed Shared Memory on Ericsson Labs
Distributed Shared Memory on Ericsson LabsDistributed Shared Memory on Ericsson Labs
Distributed Shared Memory on Ericsson Labs
 
Comparison of Amoeba, Mach & Chorus: DOS
Comparison of Amoeba, Mach & Chorus: DOSComparison of Amoeba, Mach & Chorus: DOS
Comparison of Amoeba, Mach & Chorus: DOS
 
Distributed operating system
Distributed operating systemDistributed operating system
Distributed operating system
 
Coda file system tahir
Coda file system   tahirCoda file system   tahir
Coda file system tahir
 
Characteristics of a network operating system
Characteristics of a network operating systemCharacteristics of a network operating system
Characteristics of a network operating system
 
3. challenges
3. challenges3. challenges
3. challenges
 
Domain Services for Windows: Best Practices for Windows Interoperability
Domain Services for Windows: Best Practices for Windows InteroperabilityDomain Services for Windows: Best Practices for Windows Interoperability
Domain Services for Windows: Best Practices for Windows Interoperability
 
Distributed file system
Distributed file systemDistributed file system
Distributed file system
 
Chapter 1 -_characterization_of_distributed_systems
Chapter 1 -_characterization_of_distributed_systemsChapter 1 -_characterization_of_distributed_systems
Chapter 1 -_characterization_of_distributed_systems
 
Inter-Process Communication in distributed systems
Inter-Process Communication in distributed systemsInter-Process Communication in distributed systems
Inter-Process Communication in distributed systems
 
Network operating systems1
Network operating systems1Network operating systems1
Network operating systems1
 
Chapter04 new
Chapter04 newChapter04 new
Chapter04 new
 

Destacado

The art of complaining advanced 3
The art of complaining advanced 3The art of complaining advanced 3
The art of complaining advanced 3
Jennysita Chamorro
 
The art of complaining advanced 3
The art of complaining advanced 3The art of complaining advanced 3
The art of complaining advanced 3
Jennysita Chamorro
 
Brochure jayamangali april 2012
Brochure jayamangali april 2012Brochure jayamangali april 2012
Brochure jayamangali april 2012
jauntyroads
 

Destacado (17)

Zanskar brochure
Zanskar brochureZanskar brochure
Zanskar brochure
 
Onboarding
OnboardingOnboarding
Onboarding
 
On the Irula Trail
On the Irula TrailOn the Irula Trail
On the Irula Trail
 
Writing Workshop
Writing WorkshopWriting Workshop
Writing Workshop
 
Glosary
GlosaryGlosary
Glosary
 
Facebook Timeline for Brands
Facebook Timeline for BrandsFacebook Timeline for Brands
Facebook Timeline for Brands
 
MOLECULAR GENETICS
MOLECULAR GENETICSMOLECULAR GENETICS
MOLECULAR GENETICS
 
Informatica si
Informatica siInformatica si
Informatica si
 
Cell covers, cristina y virginia
Cell covers, cristina y virginiaCell covers, cristina y virginia
Cell covers, cristina y virginia
 
The art of complaining advanced 3 final
The art of complaining advanced 3 finalThe art of complaining advanced 3 final
The art of complaining advanced 3 final
 
The art of complaining advanced 3
The art of complaining advanced 3The art of complaining advanced 3
The art of complaining advanced 3
 
The art of complaining advanced 3
The art of complaining advanced 3The art of complaining advanced 3
The art of complaining advanced 3
 
Brochure jayamangali april 2012
Brochure jayamangali april 2012Brochure jayamangali april 2012
Brochure jayamangali april 2012
 
Jane Austen- Bath
Jane Austen- BathJane Austen- Bath
Jane Austen- Bath
 
Virus informáticos
Virus informáticosVirus informáticos
Virus informáticos
 
Counterfeit money
Counterfeit moneyCounterfeit money
Counterfeit money
 
The adjectives/Los adjetivos en inglés
The adjectives/Los adjetivos en inglésThe adjectives/Los adjetivos en inglés
The adjectives/Los adjetivos en inglés
 

Similar a Intro

Chapter 1 introduction
Chapter 1 introductionChapter 1 introduction
Chapter 1 introduction
Tamrat Amare
 
Chapter 1_NG_2020.ppt
Chapter 1_NG_2020.pptChapter 1_NG_2020.ppt
Chapter 1_NG_2020.ppt
MrVMNair
 

Similar a Intro (20)

Chapter-1-IntroDistributeddffsfdfsdf-1.pptx
Chapter-1-IntroDistributeddffsfdfsdf-1.pptxChapter-1-IntroDistributeddffsfdfsdf-1.pptx
Chapter-1-IntroDistributeddffsfdfsdf-1.pptx
 
istributed system
istributed systemistributed system
istributed system
 
distributed system original.pdf
distributed system original.pdfdistributed system original.pdf
distributed system original.pdf
 
Chapter 1 introduction
Chapter 1 introductionChapter 1 introduction
Chapter 1 introduction
 
Unit 2(oss) (1)
Unit 2(oss) (1)Unit 2(oss) (1)
Unit 2(oss) (1)
 
Distributed Systems.pptx
Distributed Systems.pptxDistributed Systems.pptx
Distributed Systems.pptx
 
Distributed Operating System.pptx
Distributed Operating System.pptxDistributed Operating System.pptx
Distributed Operating System.pptx
 
Chapter 1_NG_2020.ppt
Chapter 1_NG_2020.pptChapter 1_NG_2020.ppt
Chapter 1_NG_2020.ppt
 
Distributed systems and scalability rules
Distributed systems and scalability rulesDistributed systems and scalability rules
Distributed systems and scalability rules
 
Chapter 1-Introduction.ppt
Chapter 1-Introduction.pptChapter 1-Introduction.ppt
Chapter 1-Introduction.ppt
 
Introduction
IntroductionIntroduction
Introduction
 
20IT703_PDS_PPT_Unit_I.ppt
20IT703_PDS_PPT_Unit_I.ppt20IT703_PDS_PPT_Unit_I.ppt
20IT703_PDS_PPT_Unit_I.ppt
 
CSI-503 - 11.Distributed Operating System
CSI-503 - 11.Distributed Operating SystemCSI-503 - 11.Distributed Operating System
CSI-503 - 11.Distributed Operating System
 
Chapter One.ppt
Chapter One.pptChapter One.ppt
Chapter One.ppt
 
Chap 01
Chap 01Chap 01
Chap 01
 
Chap 01
Chap 01Chap 01
Chap 01
 
Chapter 1-Introduction.ppt
Chapter 1-Introduction.pptChapter 1-Introduction.ppt
Chapter 1-Introduction.ppt
 
Distributed Operating System.pptx
Distributed Operating System.pptxDistributed Operating System.pptx
Distributed Operating System.pptx
 
Lect 1 Distributed System.pptx
Lect 1 Distributed System.pptxLect 1 Distributed System.pptx
Lect 1 Distributed System.pptx
 
Big Data Storage Concepts from the "Big Data concepts Technology and Architec...
Big Data Storage Concepts from the "Big Data concepts Technology and Architec...Big Data Storage Concepts from the "Big Data concepts Technology and Architec...
Big Data Storage Concepts from the "Big Data concepts Technology and Architec...
 

Último

Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire businessWhy Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
panagenda
 
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Victor Rentea
 

Último (20)

Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost SavingRepurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
 
Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire businessWhy Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : UncertaintyArtificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
 
Six Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal OntologySix Myths about Ontologies: The Basics of Formal Ontology
Six Myths about Ontologies: The Basics of Formal Ontology
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
 
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
 
presentation ICT roal in 21st century education
presentation ICT roal in 21st century educationpresentation ICT roal in 21st century education
presentation ICT roal in 21st century education
 
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 AmsterdamDEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam
 
MS Copilot expands with MS Graph connectors
MS Copilot expands with MS Graph connectorsMS Copilot expands with MS Graph connectors
MS Copilot expands with MS Graph connectors
 
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, AdobeApidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
 
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
Navigating the Deluge_ Dubai Floods and the Resilience of Dubai International...
 
WSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering DevelopersWSO2's API Vision: Unifying Control, Empowering Developers
WSO2's API Vision: Unifying Control, Empowering Developers
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a Fresher
 
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemkeProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWEREMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
 
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 

Intro

  • 1. CS4513 Distributed Computer Systems Introduction (Ch 1: 1.1-1.2, 1.4-1.5)
  • 2. Outline • Overview • Goals • Software • Client Server
  • 3. 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.
  • 4. 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
  • 5. 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.
  • 6. 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
  • 7. 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
  • 8. Scaling Techniques: Distribution 1.5 Example: DNS name space into zones (nl.vu.cs.fluit – z1 gives address of vu gives address of cs) Example: The Web
  • 9. 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: akamai – Example: Caching is a replication decision made by client • Issue: Consistency of replicated information – Example: Web Browser cache
  • 10. Outline • Overview (done) • Goals (done) • Software ← • Client Server
  • 11. 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
  • 12. Uniprocessor Operating Systems • Separating applications from operating system code through a microkernel – Can extend to multiple computers
  • 13. Multicomputer Operating Systems • But no longer have shared memory – Can try to provide distributed shared memory • Tough, coming up – Can provide message passing
  • 14. Multicomputer Operating Systems (optional) (optional) • Message passing primitives vary widely between systems – Example: consider buffering and synchronization
  • 15. Multicomputer Operating Systems Reliable comm. Synchronization point Send buffer guaranteed? Block sender until buffer not full Yes Not necessary Block sender until message sent No Not necessary Block sender until message received No Necessary Block sender until message delivered No Necessary • Relation between blocking, buffering, and reliable communications. • These issues make synchronization harder. It was easier when we had shared memory. – So … distributed shared memory
  • 16. Distributed Shared Memory Systems a) Pages of address space distributed among four machines c) Situation after CPU 1 references page 10 e) Situation if page 10 is read only and replication is used
  • 17. Distributed Shared Memory Systems • Issue: how large should page sizes be? What are the tradeoffs? • Overall, DSM systems have struggled to provide efficiency and convenience (and been around 15 years) – For higher-performance, typically still do message passing – Likely will remain that way
  • 18. Network Operating System • OSes can be different (Windows or Linux) • Typical services: rlogin, rcp – Fairly primitive way to share files
  • 19. 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)
  • 20. 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
  • 21. Positioning Middleware • Network OS not transparent. Distributed OS not independent computers. – Middleware can help • Much middleware built in-house to help use networked operating systems (distributed transactions, better comm, RPC) • Unfortunately, many different standards
  • 22. Middleware and Openness 1.23 • 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. – If different, compatibility issues – If incomplete, then users build their own or use lower-layer services (frowned upon)
  • 23. Comparison between Systems Distributed OS Network Middleware- Item Multiproc. Multicomp. OS based OS Degree of transparency Very High High Low High Same OS on all nodes Yes Yes No No Number of copies of OS 1 N N N Basis for communication Shared memory Messages Files Model specific Resource management Global, central Global, distributed Per node Per node Scalability No Moderately Yes Varies Openness Closed Closed Open Open • DOS most transparent, but closed and only moderately scalable • NOS not so transparent, but open and scalable • Middleware provides a bit more transparency than NOS
  • 24. Outline • Overview (done) • Goals (done) • Software (done) • Client Server ←
  • 25. Clients and Servers • Thus far, have not talked about organization of processes – Again, many choices but most agree upon 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 (apps on Internet) • Not always appropriate for high-speed LAN connection (4513)
  • 26. Example Client and Server: Header • Used by both the client and server.
  • 27. Example Client and Server: Server
  • 28. Example Client and Server: Client • One issue, is how to clearly differentiate
  • 29. 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
  • 30. Multitiered Architectures • Thin client (a) to Fat client (e) – (d) and (e) popular for NOS environments
  • 31. Multitiered Architectures: 3 tiers • Server may act as a client – Example would be transaction monitor across multiple databases
  • 32. Modern Architectures: Horizontal • Rather than vertical, distribute servers across nodes – Example of Web server “farm” for load balancing – Clients, too (peer-to-peer systems)