The DOI matches its Crossref record; 12 of the 12 references it cites were found in a registry or an index.
Experiences with the Amoeba Distributed Operating System
Open accessAbstract
The Amoeba project is a research effort aimed at understanding how to connect multiple computers in a seamless way [16, 17, 26, 27, 31]. The basic idea is to provide the users with the illusion of a single powerful timesharing system, when, in fact, the system is implemented on a collection of machines, potentially distributed among several countries. This research has led to the design and implementation of the Amoeba distributed operating system, which is being used as a prototype and vehicle for further research. In this article we will describe the current state of the system (Amoeba 4.0), and show some of the lessons we have learned designing and using it over the past eight years. We will also discuss how this experience has influenced our plans for the next version, Amoeba 5.0. Amoeba was originally designed and implemented at the Vrije Universiteit in Amsterdam, and is now being jointly developed there and at the Centrum voor Wiskunde en Informatica, also in Amsterdam. The chief goal of this work is to build a distributed system that is transparent to the users. This concept can best be illustrated by contrasting it with a network operating system, in which each machine retains its own identity. With a network operating system, each user logs into one specific machine—his home machine. When a program is started, it executes on the home machine, unless the user gives an explicit command to run it elsewhere. Similarly, files are local unless a remote file system is explicitly mounted or files are explicitly copied. In short, the user is clearly aware that multiple independent computers exist, and must deal with them explicitly. In contrast, users effectively log into a transparent distributed system as a whole, rather than to any specific machine. When a program is run, the system—not the user—decides upon the best place to run it. The user is not even aware of this choice. Finally, there is a single, system-wide file system. The files in a single directory may be located on different machines, possibly in different countries. There is no concept of file transfer, uploading or downloading from servers, or mounting remote file systems. A file's position in the directory hierarchy has no relation to its location. The remainder of this article will describe Amoeba and the lessons we have learned from building it. In the next section, we will give a technical overview of Amoeba as it currently stands. Since Amoeba uses the client-server model, we will then describe some of the more important servers that have been implemented so far. This is followed by a description of how wide-area networks are handled. Then we will discuss a number of applications that run on Amoeba. Measurements have shown Amoeba to be fast, so we will present some of our data. After that, we will discuss the successes and failures we have encountered, so that others may profit from those ideas that have worked out well and avoid those that have not. Finally we conclude with a very brief comparison between Amoeba and other systems. Before describing the software, however, it is worth saying something about the system architecture on which Amoeba runs.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Branch-and-Bound Methods: A Survey
Lawler, E. L., & Wood, D. E. (1966) · Operations Research · doi:10.1287/opre.14.4.699 · Cited by 1,997
Implementing remote procedure calls
Birrell, A. D., & Nelson, B. J. (1984) · ACM Transactions on Computer Systems · doi:10.1145/2080.357392 · Cited by 1,829
Tanenbaum, A. S., & Van Renesse, R. (1985) · ACM Computing Surveys · doi:10.1145/6041.6074 · Cited by 990
Self-citationMake — a program for maintaining computer programs
Feldman, S. I. (1979) · Software: Practice and Experience · doi:10.1002/spe.4380090402 · Cited by 787
Programming semantics for multiprogrammed computations
Dennis, J. B., & Van Horn, E. C. (1966) · Communications of the ACM · doi:10.1145/365230.365252 · Cited by 575
The Sprite network operating system
Ousterhout, J. K., Cherenson, A. R., Douglis, F., Nelson, M. N., & Welch, B. B. (1988) · Computer · doi:10.1109/2.16 · Cited by 460
Cheriton, D. (1988) · Communications of the ACM · doi:10.1145/42392.42400 · Cited by 431
Amoeba: a distributed operating system for the 1990s
Mullender, S. J., van Rossum, G., Tananbaum, A. S., van Renesse, R., & van Staveren, H. (1990) · Computer · doi:10.1109/2.53354 · Cited by 406
Self-citationOperating system support for database management
Stonebraker, M. (1981) · Communications of the ACM · doi:10.1145/358699.358703 · Cited by 382
A user authentication scheme not requiring secrecy in the computer
Evans, A., Kantrowitz, W., & Weiss, E. (1974) · Communications of the ACM · doi:10.1145/361082.361087 · Cited by 174
Cited by
Exokernel: an operating system architecture for application-level resource management
Engler, D. R., Kaashoek, M. F., & O'Toole, J. (1995) · Proceedings of the fifteenth ACM symposium on Operating systems principles - SOSP '95 · doi:10.1145/224056.224076 · Cited by 1,118
Milojičić, D. S., Douglis, F., Paindaveine, Y., Wheeler, R., & Zhou, S. (2000) · ACM Computing Surveys · doi:10.1145/367701.367728 · Cited by 470
Exploiting process lifetime distributions for dynamic load balancing
Harchol-Balter, M., & Downey, A. B. (1997) · ACM Transactions on Computer Systems · doi:10.1145/263326.263344 · Cited by 442
EROS: a fast capability system
Shapiro, J. S., Smith, J. M., & Farber, D. J. (1999) · Proceedings of the seventeenth ACM symposium on Operating systems principles · doi:10.1145/319151.319163 · Cited by 364
Labels and event processes in the asbestos operating system
Efstathopoulos, P., Krohn, M., VanDeBogart, S., Frey, C., Ziegler, D., Kohler, E., Mazières, D., Kaashoek, F., & Morris, R. (2005) · ACM SIGOPS Operating Systems Review · doi:10.1145/1095809.1095813 · Cited by 330
Metadata
- Authors
- Tanenbaum, A. S., Renesse, R. V., Staveren, H. V., Sharp, G. J., Mullender, S. J., Jansen, J., & Rossum, G. V.
- Venue
- Classic Operating Systems
- Publisher
- Springer New York
- Published
- 2001
- Volume
- 33
- Issue
- 12
- Pages
- 550-586
- OpenAlex
- W2141228336
- Cited by
- 311
- References
- 12
- FWCI
- 48.05
- Type
- book chapter
- Language
- en
- Open access
- bronze
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Experiences with the Amoeba Distributed Operating System. https://app.cochat.ai/papers/10.1007/978-1-4757-3510-9_25
- The paper
- Tanenbaum, A. S., Renesse, R. V., Staveren, H. V., Sharp, G. J., Mullender, S. J., Jansen, J., & Rossum, G. V. (2001). Experiences with the Amoeba Distributed Operating System. Classic Operating Systems. https://doi.org/10.1007/978-1-4757-3510-9_25
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.