Professional Documents
Culture Documents
Unit 1 Part1
Unit 1 Part1
CHAPTER 1
system Two aspects: (1) Independent computers and (2) Single system - middleware..
2. A distributed system consists of multiple autonomous computers that communicate
through a computer network. The computers interact with each other in order to achieve a common goal. A computer program that runs in a distributed system is called a distributed program, and distributed programming is the process of writing such programs.
3. A distributed system consists of a collection of autonomous computers, connected
through a network and distribution middleware, which enables computers to coordinate their activities and to share the resources of the system, so that users perceive the system as a single, integrated computing facility.
Chapter 1 Page1/4
Examples
The world wide web information, resource sharing Clusters, Network of workstations Distributed manufacturing system (e.g., automated assembly line) Network of branch office computers -Information system to handle automatic processing of orders Network of embedded systems New Cell processor (PlayStation 3)
Security
2.3. Reliability Long -term data preservation and backup (replication) at different locations.
Mahesh Kumar Chouhan,( A.P. Dept of CSE) Chapter 1 Page2/4
2.4. Scalability Addition of more resources to increase performance or availability. 2.5. Economy Sharing of resources by many entities to help reduce the cost of ownership. As a consequence of these features, the various entities in a distributed system can operate concurrently and possibly autonomously. Tasks are carried out independently and actions are co-ordinated at well-defined stages by exchanging messages. Also, entities are heterogenous, and failures are independent. Generally, there is no single process, or entity, that has the knowledge of the entire state of the system
4.Transparency
Goal motivated by the desire to hide all irrelevant system-dependent details from the user, whenever possible. It is more important in distributed systems due to higher implementation complexities. Shielding the system-dependent information from the users is a trade-off between simplicity and effectiveness. Access transparency - accessing both local and remote system objects in a uniform way. Location transparency - no awareness of object locations. Sometimes called name transparency. Migration transparency - ability to move an object to a different location without changing its name; also called location independence. Concurrency transparency - allow the sharing of objects without interference. Replication transparency - consistency of multiple instances (or partitioning) of files and data. Parallelism transparency - parallel activities without users knowing how, when and where. Failure transparency - fault tolerance. Performance transparency - attempts to achieve a consistent and predictable performance level even with changes of the system structure or load distribution.
Chapter 1 Page3/4
1.
2.
3.
4. 5.
6.
7. 8.
9. 10.
Size transparency - modularity and scalability. Revision transparency - vertical growth of the system.
Chapter 1 Page4/4