This Article 
 Bibliographic References 
 Add to: 
An Overview of the Nexus Distributed Operating System Design
June 1989 (vol. 15 no. 6)
pp. 686-694

Nexus is a distributed operating system designed to support experimental research in fault-tolerance techniques and object-oriented programming in distributed systems. The Nexus programming environment consists of objects, which are instances of abstract data types. Inheritance of types and multiple implementations for a type are supported by the system. Operations on objects are invoked, based on the remote-procedure-call paradigm and executed as atomic actions with provisions for application-controlled checkpointing and restart within actions. Nexus also supports parallel remote procedure calls. Interobject communication and location transparency in accessing objects is supported by the Nexus kernel.

[1] G. T. Almes, A. P. Black, E. D. Lazowska, and J. D. Noe, "The Eden system: A technical review,"IEEE Trans. Software Eng., vol. SE-11, pp. 43-59, Jan. 1985.
[2] K. P. Birman, T. A. Joseph, T. Raeuchle, and A. E. Abbadi, "Implementing fault-tolerant distributed objects,"IEEE Trans. Software Eng., vol. SE-11, no. 6, pp. 502-508, June 1985.
[3] A. D. Birrell and B. J. Nelson, "Implementing remote procedure calls,"ACM Trans. Comp. Syst., vol. 2, no. 1, pp. 39-59, Feb. 1984.
[4] A. Black, "Supporting Distributed Applications: Experience with Eden,"Proc. 10th ACM Symp. Operating Systems Principles, Dec. 1985, pp. 181-193.
[5] C.-K. Chan and A. Tripathi, "Design and implementation of the Concurrent C system," Dep. Comput. Sci., Univ. Minnesota, Minneapolis, Oct. 1987.
[6] D. Cheriton, "The V kernel: A software base for distributed systems,"IEEE Software, pp. 19-42, Apr. 1984.
[7] K. P. Eswaran, J. N. Gray, R. A. Lorie, and I. L. Traiger, "The notions of consistency and predicate locks in a database system,"Commun. ACM, vol. 19, no. 11, pp. 624-633, Nov. 1976.
[8] M. Fischer and A. Michael, "Sacrificing serializability to attain high availability of data in an unreliable network," inProc. 1st Symp. Principles Database Systems, Mar. 1982, pp. 70-75.
[9] H. Garcia-Molina, "Using semantic knowledge for transaction processing in a distributed database,"ACM Trans. Database Syst., vol. 8, no. 2, June 1983.
[10] A. Goldberg and D. Robson,Smalltalk80: The Language and Its Implementation. Reading, MA: Addison-Wesley, May 1983.
[11] T. Haerder and K. Rothermel, "Concepts in transaction recovery in nested transactions," inProc. ACM SIGMOD 1987 Ann. Conf., May 27-29, 1987, pp. 239-248.
[12] T. Haerder and A. Reuter, "Principles of transaction-oriented data-base recovery,"ACM Comput. Surveys, vol. 15, pp. 287-317, Dec. 1983.
[13] B. W. Kernighan and D. M. Ritchie,The C Programming Language. Englewood Cliffs, NJ: Prentice-Hall, 1978.
[14] B. Lampson, "Atomic transactions," inDistributed Systems: Architecture and Implementation(Lecture Notes in Computer Science, vol. 105). Berlin: Springer-Verlag, 1981, pp. 246-265.
[15] B. Liskov, "Overview of the Argus language and system," Lab. Comput. Sci., MIT, Cambridge, MA, Feb. 1984.
[16] D. B. Lomet, "Process structuring synchronization, and recovery using atomic actions,"SIGPLAN Notices, vol. 12, pp. 128-137, 1977.
[17] M. S. McKendry, "Clouds: A fault-tolerant distributed operating system," Georgia Inst. Technol., Tech. Rep. GIT-ICS-84, 1984.
[18] J. E. B. Moss, "Nested transactions: An approach to reliable distributed computing," Massachusetts Inst. Technol. Lab. Comput. Sci., Tech. Rep. MIT/LCS/TR-260, Apr. 1981.
[19] B. J. Nelson, "Remote procedure call," Dep. Comput. Sci., Carnegie-Mellon Univ., Tech. Rep., May 1981.
[20] G.J. Popek and B.J. Walker,The Locus Distributed System Architecture, MIT Press, Cambridge, Mass., 1985.
[21] B. Randell, "System structure for software fault tolerance,"IEEE Trans. Software Eng., vol. SE-1, no. 2, pp. 220-232, June 1975.
[22] D.J. Rosenkrantz, R.E. Stearns, and P.M. Lewis, II, "System level concurrency control for distributed database systems,"ACM Trans. Database Syst., vol. 3, pp. 178-198, June 1978.
[23] A. Tripathi and Z. Attia, "Synchronization of nested actions," Dep. Comput. Sci., Univ. Minnesota, Tech. Rep., Oct. 1988.
[24] B. Walter, "Nested transactions with multiple commit points: An approach to the structuring of advanced database applications," inProc. 10th Int. Conf. Very Large Data Bases, Aug. 27-31, 1984, pp. 161- 171.
[25] M. J. Weinstein, T. W. Page, Jr., B. K. Livezey, and G. J. Popek, "Transactions and synchronization in a distributed operating system," inProc. 10th ACM Symp. Operating Systems Principles, vol. 19, no. 5, pp. 115-126, Dec. 1985.

Index Terms:
interobject communication; object access; inheritance; Nexus distributed operating system design; experimental research; fault-tolerance techniques; object-oriented programming; Nexus programming environment; abstract data types; multiple implementations; remote-procedure-call paradigm; atomic actions; application-controlled checkpointing; restart; parallel remote procedure calls; location transparency; Nexus kernel; computer communications software; data structures; distributed processing; fault tolerant computing; object-oriented programming; operating systems (computers); programming environments
A.R. Tripathi, "An Overview of the Nexus Distributed Operating System Design," IEEE Transactions on Software Engineering, vol. 15, no. 6, pp. 686-694, June 1989, doi:10.1109/32.24722
Usage of this product signifies your acceptance of the Terms of Use.