The encyclopedia · Software & IT · Technical decision · 1984–1989
Sun's NFS became the file-sharing standard by staying stateless and open
Sun published NFS as an open spec with a stateless server, and it beat rival Unix file systems to become the standard.
Sun Microsystems
the move
By 1984, workstation vendors each had their own way of reaching files on other machines, and none of them worked together. Sun Microsystems wanted its new workstations to share files over a network and wanted rivals to join instead of fight, so it built a simple distributed file system of its own.
NFS kept the server stateless: every request carries the file handle and credentials it needs, so the server tracks nothing between calls. A client or server can crash and restart without any repair protocol, because there is no state to resynchronize. That design also made the protocol simple enough to implement quickly.
Sun then published the specification as RFC 1094 in March 1989 with distribution of the memo unlimited, and shipped NFS in SunOS. Rivals could implement it freely, and by the 1990s NFS was the standard way Unix machines shared files, while the more ambitious Andrew File System never matched its commercial reach.
why it works
- A stateless server survives crashes without recovery state
- Publishing the spec as an RFC let every vendor implement it
- Shipping NFS in SunOS gave it an immediate installed base
- Simplicity beat feature-rich rivals that were harder to deploy
what transfers
If you want a protocol to win, make the hard part stateless so it fails cheaply, and give the specification away — adoption beats control.
what came after
Sun handed change control of NFS to the IETF, which specified NFSv3 and then NFSv4 (RFC 3010, December 2000). Network-attached storage and every major operating system support it, and by the 21st century AFS and DCE's DFS had achieved nothing like its commercial success.
references
spotted an error? The archive wants to know.