ACM Home Page
Please provide us with feedback. Feedback
Configuring distributed systems
Full text PdfPdf (406 KB)
Source ACM SIGOPS European Workshop archive
Proceedings of the 5th workshop on ACM SIGOPS European workshop: Models and paradigms for distributed systems structuring table of contents
Mont Saint-Michel, France
SESSION: Session table of contents
Pages: 1 - 5  
Year of Publication: 1992
Authors
Jeff Kramer  Imperial College of Science, Technology and Medicine, London
Jeff Magee  Imperial College of Science, Technology and Medicine, London
Morris Sloman  Imperial College of Science, Technology and Medicine, London
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 19,   Citation Count: 8
Additional Information:

abstract   references   cited by   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/506378.506406
What is a DOI?

ABSTRACT

Distributed systems are constructed from a set of computational components which are bound together to interact and communicate to achieve some over all objective. In this paper, we examine the issues related to system configuration, particularly those related to component binding. We argue that there is a need for tools to aid the initial construction and subsequent management of the structure of distributed systems.Currently, distributed systems are most commonly structured using a client/server approach. Servers register the service they provide by installing the name and type of the service together with a reference to that service in a distinguished server generally known as a name server. Clients bind to a particular service by looking up the reference in a name server (the reference to which must be well known). Once the client has retrieved the service reference, the service may be directly invoked (although, if the reference is location independent, it may require translation to an address). ANSA[1] is an example of a distributed systems environment which conforms to this paradigm with the extension of providing a more general service than name to reference translation via its Traders. Traders provide the ability to locate services by attribute in addition to simple name lookup.Problems with the client/server approach arise when the systems we wish to construct have a more complex interconnection structure than the simple many-to-one interconnection pattern which the approach directly supports. In particular, where the distributed program is more sensibly viewed as a set of agents with peer-to-peer connections. An example is the way applications may be constructed under Unix from a pipeline of filter processes. Although all reasonable systems allow servers to be the client for other services, the interconnection process becomes tortuous. It is the authors view that as distributed systems mature and become more complex, as servers themselves are realised by distributed multi-agent programs, this problem will become more acute.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
ANSAware Release 3.0 Reference Manual, Architecture Projects Management Ltd, Poseidon House, Castle Park, Cambridge, CB3 0RD, 1991.
 
2
 
3
J. Magee, N. Dulay and J. Kramer, "Structuring Parallel and Distributed Programs", Proceedings of IEE International Workshop on Configurable Distributed Systems, Imperial College, March 1992.
 
4
REX Technical Annexe (1989), ESPRIT Project 2080, European Economic Commission.
 
5
F. Christian, " Automatic Reconfiguration in the Presence of Failures", Proceedings of IEE International Workshop on Configurable Distributed Systems, Imperial College, March 1992.

CITED BY  8
Collaborative Colleagues:
Jeff Kramer: colleagues
Jeff Magee: colleagues
Morris Sloman: colleagues