Architectures ./~course/cs501/2012 Hongfei Yan School of EECS, Peking University 2/15/2012 Contents Chapter ? 01: Introduction ? 02: Architectures ? 03: Processes ? 04: Communication ? 05: Naming ? 06: Synchronization ? 07: Consistency & Replication ? 08: Fault Tolerance ? 09: Security ? 10: Distributed Object-Based Systems ? 11: Distributed File Systems ? 12: Distributed Web-Based Systems ? 13: Distributed Coordination-Based Systems 02: Architectures ? Architectural styles ? System architectures ? Architectures versus middleware ? Self-management in distributed systems What is a Distributed System? You know when you have one …… when the failure of puter you ’ ve never heard of stops you from getting any work done ( ) A distributed system is: ? a collection of puters that appears to its users as a single coherent system Definition of a Distributed System (II) ? Independent hardware installations ? Uniform software layer (middleware) Note : the middleware layer extends over multiple machines Architectural Style ? A architectural style is formulated in terms ponents, ? the way ponents are connected to each other, ? the data exchanged ponents, and finally ? show these elements are jointly configured into a system. ? A component is a modular unit with ? well-defined required and provided interfaces ? that is replaceable within its environment. ? A connector is a mechanism that munication, coordination, or cooperation ponents. ? ., a connector can be formed by the facilities for remote procedure call, Message passing, or streaming data Architectural styles Several Architecutre Styles Using components and connectors , we e to various configurations, in turn have been classified into architectural sytles. ? Layered architectures ? Object-based architectures ? Data-centered architectures ? Event-based architectures Architectural styles(1/4): Layered style Observation : Layered sty
