Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Open Systems Support : Interoperability: The Ability of Two Different Systems or Applications To

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 15

Open Systems Support … 1

 Interoperability: the ability of two different systems or applications to


work together
 A process that needs a service should be able to talk to any process that
provides the service.
 Multiple implementations of the same service may be provided, as long as
the interface is maintained
 Portability: an application designed to run on one distributed system can
run on another system which implements the same interface.
 Extensibility: Easy to add new components, features
2
Goal 4 - Scalability

 Dimensions that may scale:


 With respect to size
 With respect to geographical distribution
 With respect to the number of administrative organizations spanned
 A scalable system still performs well as it scales up along any of the three
dimensions.
Size Scalability 3

 Scalability is negatively affected when the system is based on


 Centralized server: one for all users
 Centralized data: a single data base for all users
 Centralized algorithms: one site collects all information, processes it,
distributes the results to all sites.
 Complete knowledge: good
 Time and network traffic: bad
4
Decentralized Algorithms

 No machine has complete information about the system state


 Machines make decisions based only on local information
 Failure of a single machine doesn’t ruin the algorithm
 There is no assumption that a global clock exists.
Geographic Scalability 5

 Early distributed systems ran on LANs, relied on synchronous


communication.
 May be too slow for wide-area networks
 Wide-area communication is unreliable, point-to-point;
 Unpredictable time delays may even affect correctness
 LAN communication is based on broadcast.
 Consider how this affects an attempt to locate a particular kind of service
 Centralized components + wide-area communication: waste of
network bandwidth
Scalability - Administrative 6

 Different domains may have different policies about resource usage, management,
security, etc.
 Trust often stops at administrative boundaries
 Requires protection from malicious attacks
Scaling Techniques 7

 Scalability affects performance more than anything else.


 Three techniques to improve scalability:
 Hiding communication latencies
 Distribution
 Replication
8
Distribution
 Instead of one centralized service, divide into parts and distribute
geographically
 Each part handles one aspect of the job
 Example: DNS namespace is organized as a tree of domains; each domain
is divided into zones; names in each zone are handled by a different name
server
 WWW consists of many (millions?) of servers
Third Scaling Technique - 9
Replication
 Replication: multiple identical copies of something
 Replicated objects may also be distributed, but aren’t necessarily.
 Replication
 Increases availability
 Improves performance through load balancing
 May avoid latency by improving proximity of resource
Types of Distributed Systems 10

 Distributed Computing Systems


 Clusters
 Grids
 Clouds
 Distributed Information Systems
 Transaction Processing Systems
 Enterprise Application Integration
 Distributed Embedded Systems
 Home systems
 Health care systems
 Sensor networks
Cluster Computing 11

 A collection of similar processors (PCs, workstations) running the


same operating system, connected by a high-speed LAN.
 Parallel computing capabilities using inexpensive PC hardware
 Replace big parallel computers (MPPs)
Cluster Types & Uses 12

 High Performance Clusters (HPC)


 run large parallel programs
 Scientific, military, engineering apps; e.g., weather modeling
 Load Balancing Clusters
 Front end processor distributes incoming requests
 server farms (e.g., at banks or popular web site)
 High Availability Clusters (HA)
 Provide redundancy – back up systems
 May be more fault tolerant than large mainframes
Cluster Computing Systems 13

 Figure 1-6. An example of a cluster computing system.

Figure 1-6. An example of a cluster computing system


Grid Computing Systems 14

 Modeled loosely on the electrical grid.


 Highly heterogeneous with respect to hardware, software, networks,
security policies, etc.
 Grids support virtual organizations: a collaboration of users who
pool resources (servers, storage, databases) and share them
 Grid software is concerned with managing sharing across
administrative domains.
Grids 15

 Similar to clusters but processors are more loosely coupled, tend to be


heterogeneous, and are not all in a central location.
 Can handle workloads similar to those on supercomputers, but grid
computers connect over a network (Internet?) and supercomputers’
CPUs connect to a high-speed internal bus/network
 Problems are broken up into parts and distributed across multiple
computers in the grid – less communication betw parts than in
clusters.

You might also like