This Article 
 Bibliographic References 
 Add to: 
The Influence of Scale on Distributed File System Design
January 1992 (vol. 18 no. 1)
pp. 1-8

The proposition that scale should be recognized as a primary factor influencing the architecture and implementation of distributed systems is validated using Andrew and Coda, two distributed file systems. Performance, operability, and security are dominant considerations in the design of these systems. Availability is a further consideration the design of Coda. Client caching, bulk data transfer, token-based mutual authentication and hierarchical organization of the protection domain have emerged as mechanisms that enhance scalability. The separation of concerns made possible by functional specialization has also proved valuable in scaling. Heterogeneity is an important by-product of growth, but the mechanisms available to cope with it are rudimentary. Physical separation of clients and servers turns out to be a critical requirement for scalability

[1] M. Accetta, G. Robertson, M. Satyanarayanan, and M. Thompson, "The design of a network-based central file system," Dept. Computer Sci., Carnegie Mellon Univ., Pittsburgh, PA, Tech. Rep. CMU-CS-80-134, 1980.
[2] D. R. Brownbridge, L. F. Marshall, and B. Randell, "The Newcastle connection,"Software Pract. Exper., vol. 12, pp. 1147-1162, 1982.
[3] M. Burrows, "Efficient data sharing," Ph.D. diss., Computer Lab., Univ. Cambridge, Dec. 1988.
[4] "VMS system software handbook," Digital Equipment Corp., Maynard, MA, 1985.
[5] A. Hisgen, A. Birrell, T. Mann, M. Schroeder, and G. Swart, "Availability and consistency trade-offs in the Echo distributed file system," inProc. 2nd IEEE Workshop on Workstation Operating Syst., Sept. 1989.
[6] J. H. Howardet al., "Scale and performance in a distributed file system,"ACM Trans. Comput. Syst., vol. 6, no. 1, Feb. 1988.
[7] J. J. Kistler and M. Satyanarayanan, "Disconnected operation in the Coda file system,"ACM Trans. Comput. Syst., vol. 10, no. 1, Feb. 1992.
[8] P. H. Levine, "The Apollo DOMAIN distributed file system," inNATO ASI Series: Theory and Practice of Distributed Operating Systems, Y. Paker, J.-P. Banatre, and M. Bozyigit, Eds. New York: Springer-Verlag, 1987.
[9] J. H. Morriset al., "Andrew: a distributed personal computing environment,"Commun. ACM, vol. 29, no. 3, Mar. 1986.
[10] S. J. Mullender, G. van Rossum, A. S. Tanenbaum, R. van Renesse, and H. van Staveren, "Amoeba: a distributed operating system for the 1990s,"IEEE Trans. Computer, vol. 23, pp. 44-53, May 1990.
[11] Roger Needham and Michael Schroeder, "Using Encryption for Authentication in Large Networks of Computers,"Comm. ACM, Vol. 21, No. 12, Dec. 1978, pp. 993- 999.
[12] M. N. Nelson, B. B. Welch, and J. K. Ousterhout, "Caching in the Sprite network file system,"ACM Trans. Comput. Syst.vol. 6, no. 1, Feb. 1988.
[13] J. Ousterhoutet al., "Trace-driven analysis of the Unix 4.2 BSD file system," inProc. 10th ACM Symp. on Operating System Principles, Dec. 1985.
[14] C. B. Pinkerton, E. D. Lazowska, D. Notkin, and J. Zahorjan, "A heterogeneous remote file system," Dept. Computer Sci., Univ. Washington, Seattle, Tech. Rep. 88-08-08, Aug. 1988.
[15] L. K. Raper, "The CMU PC Server project," Inform. Techn. Ctr., Carnegie Mellon Univ., Pittsburgh, PA, Tech. Rep. CMU-ITC-051, Feb. 1986.
[16] A. P. Rifkinet al., "RFS architectural overview," inProc. Usenix Conference(Atlanta, GA), 1986.
[17] R. Sandberg, D. Goldberg, S. Kleiman, D. Walsh, and B. Lyon, "Design and implementation of the Sun network filesystem," inProc. Usenix Conf.(Portland), 1985.
[18] M. Satyanarayan,et al., The ITC distributed file system: Principles and design," inProc. 10th Symp. Operating System Principles, Orcas Island, WA, Dec. 1985, pp. 35-50.
[19] M. Satyanarayanan, "Integrating security in a large distributed system,"ACM Trans. Comput. Syst., vol. 7, no. 3, Aug. 1989.
[20] M. Satyanarayananet al., "Coda: a highly available file system for a distributed workstation environment,"IEEE Trans. Computers, vol. 39, no. 4, Apr. 1990.
[21] M. Satyanarayanan, "Scalable, secure, and highly available distributed file access,"IEEE Computers, vol. 23, no. 5, May 1990.
[22] M. D. Schroeder, A. D. Birrell, and R. M. Needham, "Experience with Grapevine: the growth of a distributed system,"ACM Trans. Comput. Syst., vol. 2, no. 1, pp. 3-23, Feb. 1984.
[23] M. D. Schroeder, D. K. Gifford, and R. M. Needham, "A caching file system for a programmer's workstation," inProc. 10th Symp. on Operating System Principles, Dec. 1985.
[24] R. N. Sidebotham, "Volumes: the Andrew file system data structuring primitive," inProc. Eur. Unix User Group Conf., Aug. 1986 (also available as Information Techn. Ctr., Carnegie Mellon Univ., Pittsburgh, PA, Tech. Rep. CMU-ITC-053).
[25] D. C. Steere, J. J. Kistler, and M. Satyanarayanan, "Efficient user-level file cache management on the Sun Vnode interface," inProc. Usenix Conf.(Anaheim, CA), June 1990.
[26] J. G. Steiner, C. Neumann, and J. I. Schiller, "Kerberos: an authentication service for open network systems," inProc. Usenix Conf.(Dallas, TX), Feb. 1988.
[27] G. Stroud, "Introduction to TOPS,"Sun Techn., vol. 1, no. 2, Spring 1988.
[28] D. B. Terry, "Caching hints in distributed systems,"IEEE Trans. Software Eng., vol. SE-13, Jan. 1987.
[29] B. Walker et al., "The Locus Distributed Operating System,"Proc. Ninth ACM Symp. Operating Systems Principles, Oct. 1983, pp. 49-70.
[30] E. R. Zayas and C. F. Everhart, "Design and specification of the cellular Andrew environment," Inform. Techn. Ctr., Carnegie Mellon Univ., Pittsburgh, PA, Tech. Rep. CMU-ITC-070, June 1988.

Index Terms:
client caching; distributed file system design; Andrew; Coda; security; bulk data transfer; token-based mutual authentication; hierarchical organization; protection domain; scalability; functional specialization; distributed processing; file organisation
M. Satyanarayanan, "The Influence of Scale on Distributed File System Design," IEEE Transactions on Software Engineering, vol. 18, no. 1, pp. 1-8, Jan. 1992, doi:10.1109/32.120311
Usage of this product signifies your acceptance of the Terms of Use.