Distributed Computing

Unit 1 -Introduction
Lecture 1b
Scalability Aspects
Scalability can be defined with respect to the
following aspects:

Size

Geographical Area

Administrative Scalability
 Scalability Examples
Distributed systems are ubiquitous and necessary:
Web search
Financial transactions
Multiplayer games
DNS
Travel reservation systems
Embedded systems (e.g., cars)
Scalability Problems

Concept

Centralized services

Centralized data

Centralized algorithms

Examples of scalability limitations.

 Web Search
Google uses thousands of machines to
Provide search results
Run Page-Rank algorithm
Issues
Connecting large number of machines
Distributed file system
Indexing
Programming model
Scaling up when current system reaches limits
Decentralized Algorithm
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.
Scaling Techniques (1)

1.4

The difference between letting:

a) a server or
b) a client check forms as they are being filled
Scaling Techniques(2)

Hiding Communication

Distribution

Replication
Scaling Techniques (3)

1.5

An example of dividing the DNS name space into zones.

Transaction Processing Systems (1)
Example primitives for transactions.
 Transaction Processing Systems (2)
Characteristic properties of transactions:
Atomic.

Consistent

Isolated

Durable:
 Transaction Processing Systems (3)

Figure 1-9. A nested transaction.

Transaction Processing Systems (4)
Figure 1-10. The role of a TP monitor in distributed systems.
 EAI-Enterprise Application Integration

Figure 1-11. Middleware as a communication facilitator in enterprise

application integration.
Positioning Middleware
General structure of a distributed system as middleware.

1-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.
Modern Architectures
An example of horizontal distribution of a Web service.

1-31
 Electronic Health Care Systems (1)
Questions to be addressed for health care systems:
Where and how should monitored data be stored?
How can we prevent loss of crucial data?
What infrastructure is needed to generate and propagate
alerts?
How can physicians provide online feedback?
How can extreme robustness of the monitoring system be
realized?
What are the security issues and how can the proper policies
be enforced?
 Electronic Health Care Systems (2)

Figure 1-12. Monitoring a person in a pervasive electronic health care system, using (a) a local hub or
(b) a continuous wireless connection.
Pitfalls
False assumptions that developers make when developing a
distributed application :
1. The network is reliable.
2. The network is secure.
3. The network is homogeneous.
4. The topology does not change.
5. Latency is zero.
6. Bandwidth is infinite.
7. Transport cost is zero.
8. There is one administrator.
End of Unit 1 Part b