TL;DR: An overview of the basic design of CDCS is given, an outline of its evolution and a description of the distributed systems research projects that were based on it are given.
Abstract: The Cambridge Distributed Computing System (CDCS) was designed some ten years ago and was in everyday use at the Computer Laboratory until December 1988. An overview of the basic design of CDCS is given, an outline of its evolution and a description of the distributed systems research projects that were based on it. Experience has shown that a design based on a processor bank leads to a flexible and extensible distributed system.
TL;DR: The DAPHNE system is a collection of tools and run-time support creating a network operating system interface for distributed programming using Modula-2, which accomodates hardware and operating system heterogeneity without necessarily unifying heterogeneous system features.
Abstract: The DAPHNE system is a collection of tools and run-time support creating a network operating system interface for distributed programming using Modula-2. DAPHNE accomodates hardware and operating system heterogeneity without necessarily unifying heterogeneous system features. In describing the essentials of the DAPHNE approach we concentrate on the semantics of heterogeneous distributed programs and on the difficulties encountered in implementing DAPHNE on top of standard operating systems. Several requirements for the functionality of system interfaces are derived.
TL;DR: The authors propose models for defining the availability metric, a meaningful indicator of a distributed computing environment's performance from the reliability point of view that can also be used to efficiently design, engineer, and monitor a distributed Computing environment's activities.
Abstract: The authors propose models for defining the availability metric of a distributed computing environment. The metric is a meaningful indicator of a distributed computing environment's performance from the reliability point of view. The proposed models can also be used to efficiently design, engineer, and monitor a distributed computing environment's activities. The models are general and can be applied to any distributed computing environment for availability evaluation. >
TL;DR: In this paper, the authors classified end users into six distinct types, each of which needs differentiated education, support, and control from the Information Systems (I/S) function, and paid close attention to the need to involve functional support personnel in the I/S end user management process.
Abstract: End users can be classified into six distinct types. Each of them needs differentiated education, support, and control from the Information Systems function. To support a large number of their applications a new computing environment, “the third environment” must be developed by Information Systems (I/S) management. Close attention must also be paid by I/S management to the need to involve “functional support personnel” (end users in each functional area who spend most of their time programming and aiding other end users) in the I/S end user management process.
TL;DR: A task allocation model that allocates application tasks among processors in distributed computing systems satisfying: 1) minimum interprocessor communication cost, 2) balanced utilization of each processor, and 3) all engineering application requirements is presented.