1. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S. TANENBAUM MAARTEN VAN STEEN Chapter 2 ARCHITECTURES

2. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 System Models Physical model –Hardware – instruction set –Take what you can get (you don’t drive) –FPGA vs. faster generation of CPU/GPU –Network and machines Distributed architecture model –Logical distribution of tasks, storage Conceptual/Fundamental model –Interaction model –Approaches to basic requirements

3. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Architecture Models & Elements Communication Entities –Objects –Components –Services Communication Paradigm –IPC – message passing Synchronous/asynch send/receive Unicast/multicast Reliability –Remote invocation (RMI/RPC) –Indirect communication Key is good abstraction!

4. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Examples of Abstractions Operating system –Hardware/devices –Drivers –Services Software –Primitives –Layers of abstraction - middleware Communication –Protocol layers –Distributed communication models

5. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Need for Abstraction Decomposition –Simplify components –Combine related concerns/responsibilities –Maintain sanity Convenience –Isolation of issues –Build desired mechanisms –Migration of components Correctness –Modularity – debugging, verification –Isolation of implementation

6. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Fundamental Models Interaction model –Who talks to whom –How do they interact? Communication model –Synchronous – blocking –Client-server Synchronous services over asynch comm Useful at thread level Be cautious with actors - scaling –Group communication

7. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 OS vs. Middleware Operating system –Efficiency – low overhead –Transparency –Requires homogeneity (incl. admin) Middleware (e.g. DCE, CORBA, SOA) –OS independent - portable –Libraries OS also uses libraries –Higher communication latency More layers

8. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Architectural Styles (1) Important styles of architecture for distributed systems Layered architectures Object-based architectures Data-centered architectures Event-based architectures

9. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Architectural Styles (2) Figure 2-1. The (a) layered architectural style and …

10. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Architectural Styles (3) Figure 2-1. (b) The object-based architectural style.

11. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Architectural Styles (4) Figure 2-2. (a) The event-based architectural style and …

12. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Architectural Styles (5) Figure 2-2. (b) The shared data-space architectural style.

13. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Application Layering (1) Recall previously mentioned layers of architectural style The user-interface level The processing level The data level

14. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Application Layering (2) Figure 2-4. The simplified organization of an Internet search engine into three different layers.

15. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Multitiered Architectures (1) The simplest organization is to have only two types of machines: A client machine containing only the programs implementing (part of) the user- interface level A server machine containing the rest, –the programs implementing the processing and data level

16. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Multitiered Architectures (2) Figure 2-5. Alternative client-server organizations (a)–(e).

17. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Centralized Architectures Figure 2-3. General interaction between a client and a server. Note that client-server interaction can also be used for multi- threaded, asynchronous process models

18. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Multitiered Architectures (3) Figure 2-6. An example of a server acting as client.

19. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Peer-to-peer Architectures P2P implies all are equals Scales well (usually) – more nodes = more to do the work, more connections Organization is an issue P2P Architecture Types Unstructured – try to keep a certain number of logical neighbors; circulate Structured – try to maintain a particular structure of overlay network Often useful to have peers evolve distinct roles, or use unstructured to evolve structure

20. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Structured Peer-to-Peer Architectures (1) Figure 2-7. The mapping of data items onto nodes in Chord. Distributed Hash Table (DHT) Data items are hashed to obtain key, which is then used to place items in hash table Portions of the hash table assigned to each participating node

21. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Structured Peer-to-Peer Architectures (2) Figure 2-8. (a) The mapping of data items onto nodes in CAN. Multi-dimensional search: data items assigned a point in k-dimensional Cartesian space, regions assigned to nodes

22. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Structured Peer-to-Peer Architectures (3) A new participant picks a random point in space, contacts node responsible for that point, which then splits its space between it and the new node Merge space when node leaves, reassign resp. Figure 2-8. (b) Splitting a region when a node joins.

23. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Unstructured Peer-to-Peer Architectures (1) Figure 2-9. (a) The steps taken by the active thread. Push or pull alone often leads to partition

24. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Unstructured Peer-to-Peer Architectures (2) Figure 2-9. (b) The steps take by the passive thread Goal: maintain partial view of c live neighbors

25. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Topology Management of Overlay Networks (1) Figure 2-10. A two-layered approach for constructing and maintaining specific overlay topologies using techniques from unstructured peer-to-peer systems.

26. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Topology Management of Overlay Networks (2) Figure 2-11. Generating a specific overlay network using a two- layered unstructured peer-to-peer system [adapted with permission from Jelasity and Babaoglu (2005)].

27. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Superpeers Figure 2-12. A hierarchical organization of nodes into a superpeer network.

28. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Superpeer Selection Qualities a superpeer should possess: Accessible Responsive Reliable These imply superpeer attributes: Internet-facing (e.g., routable IP address) Well-connected (high-speed Internet cnx) Resources (CPU speed, memory) “Near” clients (a relative attribute)

29. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Edge-Server Systems Figure 2-13. Viewing the Internet as consisting of a collection of edge servers. Akin to transportation system vs. stores, shoppers, employees, warehouses, factories, etc.

30. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Collaborative Distributed Systems (1) Figure 2-14. The principal working of BitTorrent [adapted with permission from Pouwelse et al. (2004)].

31. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Collaborative Distributed Systems (2) Globule: CDN for replication of web pages Origin server: web server providing content Broker: centralized registration server Components of Globule collaborative content distribution network: A component that can redirect client requests to other servers. A component for analyzing access patterns. A component for managing the replication of Web pages.

32. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Interceptors Figure 2-15. Using interceptors to handle remote-object invocations.

33. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 General Approaches to Adaptive Software Environment changes: need adaptation Three basic approaches to adaptive software: Separation of concerns: functional & other – Aspect-oriented s/w development Computational reflection – Self-modifying code, late binding/dynamic loading Component-based design – Composition Low success/promise ratio so far....

34. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 The Feedback Control Model Figure 2-16. The logical organization of a feedback control system.

35. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Figure 2-17. Data collection and information aggregation in Astrolabe. Example: Systems Monitoring with Astrolabe

36. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Example: Differentiating Replication Strategies in Globule (1) Figure 2-18. The edge-server model assumed by Globule.

37. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Example: Differentiating Replication Strategies in Globule (2) Figure 2-19. The dependency between prediction accuracy and trace length.

38. Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved. 0-13-239227-5 Example: Automatic Component Repair Management in Jade Steps required in a repair procedure: Terminate every binding between a component on a non-faulty node, and a component on the node that just failed. Request the node manager to start and add a new node to the domain. Configure the new node with exactly the same components as those on the crashed node. Re-establish all the bindings that were previously terminated.