130 likes | 143 Views
Learn about distribution transparency, failures recovery, scalability techniques, and communication services in distributed computing systems. Understand the benefits of an open distributed system.
E N D
EEC-681/781Distributed Computing Systems Discussion#1 (Chapter 1&2) Wenbing Zhao wenbing@ieee.org
Q1: What is the role of middleware in a distributed system? EEC-681: Distributed Computing Systems
Q2: Explain what is meant by (distribution) transparency, and give examples of different types of transparency. EEC-681: Distributed Computing Systems
Q3: Why is it sometimes so hard to hide the occurrence and recovery from failures in a distributed system? EEC-681: Distributed Computing Systems
Q4: Why is it not always a good idea to aim at implementing the highest degree of transparency possible? EEC-681: Distributed Computing Systems
Q5: What is an open distributed system and what benefits does openness provide? EEC-681: Distributed Computing Systems
Q6: Describe precisely what is meant by a scalable system. EEC-681: Distributed Computing Systems
Q7: Scalability can be achieved by applying different techniques. What are these techniques? EEC-681: Distributed Computing Systems
Q8: What is the difference between a vertical distribution and a horizontal distribution? EEC-681: Distributed Computing Systems
Q9: Why are transport-level communication services often inappropriate for building distributed applications? EEC-681: Distributed Computing Systems
Q10: Suppose you could make use of only transient synchronous communication primitives. How would you implement primitives for transient asynchronous communication? EEC-681: Distributed Computing Systems
Q11: Explain why transient synchronous communication has inherent scalability problems, and how these could be solved. EEC-681: Distributed Computing Systems
Q12. The most prominent benefit of the publish/subscribe model is the increased scalability if the number of consumers per message (created by a producer) is large. Understand this benefit by comparing the number of transport-level messages needed to propagate an application-level message to, say, 3 consumers, using the two different messaging models (queue-based and publish/subscribe). EEC-681: Distributed Computing Systems