Download Introduction - WordPress.com

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Unix security wikipedia , lookup

Distributed operating system wikipedia , lookup

Transcript
Introduction
Chapter 1
Dr.Husam Osta (9th Floor)
www.husamo.wordpress.com
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
1
Introduction
• Computer revolution started from the year 1945 (modern era)
• During the year 1985 large and expensive computers were available
• As time progressed new developments took place and two new technologies were
developed. They are
1. Powerful microprocessor (8 bit, 16 bit, 32 bit, 64 bit)
2. High speed networks
- LAN – Local area network,
- WAN– Wide area network
• The result of the above two technologies were;
1. Flexible
2. Easy to access and put together all the computing systems connected together
with high speed network.
• The above result leads to distributed systems…Than previous centralized systems.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
2
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 INFORMATION
MANAGEMENT-- CHAPTER 1
3
Definition of a Distributed System (2)
1.1
A distributed system organized as middleware.
Note that the middleware layer extends over multiple machines.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
4
Definition means..
1. Distributed systems consists of components (computer)
that are autonomous (independent, self-directing)
2. Users they are dealing with single system i.e. all the
autonomous computers need to collaborate
when autonomous computers are collaborated - we get distributed systems.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
5
Characteristic of Distributed systems
1. Resource sharing (h/w, s/w, data, files, should have resource manger)
2. Openness
3. Concurrency
4. Scalability
5. Fault Tolerance
6. Transparency
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
6
Characteristic of Dis. Systems
• Access resources and share them in a controlled and efficient way.
– Printers, computers, storage facilities, data, files, Web pages,
and networks, …
• Connecting users and resources also makes it easier to collaborate
and exchange information.
– Internet for exchanging files, mail, documents, audio, and
video
• Security is becoming increasingly important
– Little protection against spying or intrusion on communication
– Tracking communication to build up a preference profile of a
specific user
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
7
Openness
• Open distributed system – is a system that is able to interact with
services from other open systems, irrespective of the underlying
environment:
– System should conform to well-defined interfaces
– Systems should support portability of applications
– Systems should easily interoperate
• Achieving openness: The distributed system should be independent
from heterogeneity of the underlying environment:
– Hardware
– Platforms
– Languages
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
8
Openness
• Implementing openness requires support
different polices:
for
– What level of consistency do we require for client-cached data?
– Which operations do we allow downloaded code to perform?
– What level of secrecy do we require for communication?
• In implementing openness, ideally, a distributed
system should provide mechanisms that:
– Allow (dynamic) setting of caching policies
– Support different levels of trust for mobile code
– Offer different encryption algorithms
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
9
Scalability in Distributed Systems
Scalability of a system can be measured along at least three
different dimensions (Neuman, 1994):
• First, a system can be scalable with respect to its size, meaning
that we can easily add more users and resources to the system.
• Second, a geographically scalable system is one in which the
users and resources may lie far apart.
• Third, a system can be administratively scalable, among that it
can still be easy to manage even if it spans many independent
administrative organizations.
• Unfortunately, a system that is scalable in one or more of these
dimensions often exhibits some loss of performance as the
system scales up.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
10
Scalability in Distributed Systems
• Components of Scalability:
– Number of users and/or processes (size scalability)
– Maximum distance between nodes (geographical scalability)
– Number of administrative domains (administrative scalability)
• Observation: Most systems account only, to a certain extent, for
size scalability, such as powerful servers. However, the
challenge lies in geographical and administrative scalability.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
11
Scalability Problems @ size
• Decentralized algorithms:
–
–
–
–
No machine has complete information about the system state.
Machines make decisions based only on local information.
Failure of one machine does not ruin the algorithm
There is no implicit assumption that a global clock exists
12
Scalability Problems @ geography
• Synchronous communication
– A party requesting service, generally referred to as a client, blocks until a
reply is sent back.
• WANs is unreliable and Point-to-point
• LANs provide reliable communication facilities based on
broadcasting.
• Geographical scalability is strongly related to problems of
centralized solutions that hinder size scalability.
– In addition, centralized components now lead to a waste of network
resources.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
13
Scalability Problems @ administration
• It’s difficult and in many cases open questions
– Conflicting polices with respect to resource usage, management,
and security.
– E.g.,
• A domain can often be trusted by users that operate within that same
domain.
• Downloading programs such as applets in Web browsers.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
14
Distributed Transparency
• An important goal of distributed system is to hide the
fact that it’s process and resources are physically
distributed across multiple computers.
• A distributed systems that is able to present itself to
users and applications as if it were only a single
computer systems is said to be Transparent.
Different forms of transparency in a distributed system.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
15
Distributed Transparency
Types of transparancy
Transparency
Access
Description
Hide differences in data representation and how a resource is
accessed
Location
Hide where a resource is located
Migration
Hide that a resource may move to another location
Relocation
Hide that a resource may be moved to another location while in
use
Replication
Hide that a resource may be shared by several competitive users
Concurrency
Hide that a resource may be shared by several competitive users
Failure
Persistence
Hide the failure and recovery of a resource
Hide whether a (software) resource is in memory or on disk
Different forms of transparency in a distributed system.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
16
Hardware Concepts
1.6
Different basic organizations and memories in distributed computer systems
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
17
Multiprocessors (1)
1.7
A bus-based multiprocessor.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
18
Multiprocessors (2)
1.8
a) A crossbar switch
b) An omega switching network
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
19
Homogeneous Multicomputer Systems
1-9
a) Grid
b) Hypercube
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
20
Software Concepts
System
Description
Main Goal
DOS
Tightly-coupled operating system for multiprocessors and homogeneous multicomputer
Hide and manage
hardware resources
NOS
Loosely-coupled operating system for
heterogeneous multicomputer (LAN and WAN)
Offer local services
to remote clients
Additional layer atop of NOS implementing
general-purpose services
Provide distribution
transparency
Middleware
An overview of
• DOS (Distributed Operating Systems)
• NOS (Network Operating Systems)
• Middleware
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
21
Multicomputer Operating Systems (1)
1.14
General structure of a multicomputer operating system.
(DOS)
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
22
Network Operating System (1)
1-19
General structure of a network operating system. (NOS)
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
23
Network Operating System (2)
1-20
Two clients and a server in a network operating system.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
24
Positioning Middleware
1-22
General structure of a distributed system as middleware.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
25
Middleware and Openness
In an open middleware-based distributed system, protocols used by each
middleware layer should be the same, as well as the interfaces they offer to
applications.
1.23
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
26
Comparison between Systems
Item
Distributed OS
Network
OS
Middlewarebased OS
Multiproc.
Multicomp.
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
•
A comparison between multiprocessor operating systems, multicomputer operating systems,
network operating systems, and middleware based distributed systems.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
27
Clients and Servers
1.25
General interaction between a client and a server.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
28
Multitiered Architectures (2)
1-30
An example of a server acting as a client.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
29
Modern Architectures
1-31
An example of horizontal distribution of a Web service.
DISTRIBUTED INFORMATION
MANAGEMENT-- CHAPTER 1
30