DistOS 2014W Midterm Review: Difference between revisions
| Line 19: | Line 19: | ||
===Questions=== | ===Questions=== | ||
* The architecture of distributed OSs typically are some mix of peer-to-peer and hierarchies (e.g. master/slave) in the arrangement of servers. Give an example of each and explain why the choice was made (a hierarchy versus peer-to-peer). | |||
* "UNIX compatibility is increasingly sacrificed in order to improve scalability." Argue for or against. | |||
Revision as of 15:53, 25 February 2014
Themes
- Scaling
- caching
- consistency
- specialized versus general solutions
- OS abstractions
- paths not taken
- network transparency (making remote look like local)
- reliability
- fault tolerance
- redundancy
- availability
- resource sharing
- information sharing
- communication
- collaboration
- peer-to-peer versus hierarchy
- latency versus bandwidth
Questions
- The architecture of distributed OSs typically are some mix of peer-to-peer and hierarchies (e.g. master/slave) in the arrangement of servers. Give an example of each and explain why the choice was made (a hierarchy versus peer-to-peer).
- "UNIX compatibility is increasingly sacrificed in order to improve scalability." Argue for or against.