Content deleted Content added
m Bot: link specificity and minor changes |
→Features: tidy up ref |
||
Line 3:
== Features ==
AFS<ref>{{cite journal|author =Howard, J.H.|author2 =Kazar, M.L.|author3 =Nichols, S.G.|author4 =Nichols, D.A.|author5 =Satyanarayanan, M.|author6 =Sidebotham, R.N.|author7 =West, M.J.|last-author-amp =yes|title=Scale and Performance in a Distributed File System|journal=ACM Transactions on Computer Systems|volume=6|issue=1|date=February 1988|pages=51–81|doi=10.1145/35037.35059|citeseerx =10.1.1.71.5072}}</ref> has several benefits over traditional networked [[file system]]s, particularly in the areas of security and scalability. One enterprise AFS deployment at [[Morgan Stanley]] exceeds 25,000 clients.<ref>{{cite web|url=http://www-conf.slac.stanford.edu/AFSBestPractices/Slides/MorganStanley.pdf|title=When Your Business Depends On It — The Evolution of a Global File System for a Global Enterprise|first=Phillip|last=Moore|date=2004}}</ref> AFS uses [[Kerberos protocol|Kerberos]] for authentication, and implements [[access control list]]s on directories for users and groups. Each client caches files on the local filesystem for increased speed on subsequent requests for the same file. This also allows limited filesystem access in the event of a [[crash (computing)|server crash]] or a [[network outage]].
AFS uses the [[Weak consistency|Weak Consistency]] model.<ref>{{Citation
| |||