No abstract

No abstract

Abstract:Distributed systems' runtime behavior can be difficult to understand. Concurrent, distributed activity make notions of global state difficult to grasp. We focus on the runtime structure of a system, its execution architecture, and propose representing its evolution as a partially ordered set of predefined architectural event types. This representation allows a system's topology to be visualized, analyzed and constrained. The use of a predefined event types allows the execution architectures of different systems to be readily compared. INTRODUCTIONDistributed software systems consist of computational components interacting over a communications infrastructure. The executions of these systems can be highly dynamic with components being created and destroyed and the communications infrastructure undergoing continual reconfiguration. We propose to represent the evolution of the structure of such a running system, termed the execution architecture of the system, as a set of events, partially ordered by time and causality. This partial order of architectural events enables the precise analysis of the topological evolution of a system, just as a partial order of behavioral events enables a precise analysis of the functional activity of a system (Peled, Pratt et al. 1996). P. Donohoe (ed.), Software Architecture

No abstract

Designing publicly accessible and distributed information structures and coordinating distributed authors is a major challenge for most organizations. This paper presents a scaleable reference architecture for multi-author World-Wide Web (W3) servers, one important type of a distributed and publicly accessible information system. We introduce the paradigm of "lean production of information" and discuss some problems of data quality regarding W3-servers. Experiences made with a departmental W3-server designed and maintained according to the principles presented are appended as a case study.