Cs 422 - Distributed Computing: Why Should We Be Interested?
Cs 422 - Distributed Computing: Why Should We Be Interested?
Cs 422 - Distributed Computing: Why Should We Be Interested?
@ https://myclass.myvirtuallearning.org
According to ionos.com
Design Goals
• Support resource sharing
• Storage facilities, peripherals, data, files, networks, services
• Transparent distribution
Transparency Description
Access Hide differences in data representation and how an object is accessed
Location Hide where an object is located
Relocation Hide that an object may be moved to another location while in use
Migration Hide that an object may move to another location
Replication Hide that an object is replicated
Concurrency Hide that an object may be shared by several independent users
Failure Hide the failure and recovery of an object
Design Goals
• Being open
• Interoperability
• Different file system by different OS
• The role of interfaces
• Composability
• Extensibility
• Example. Caching of browsers
Storage Where is data to be cached? Typically, there will be an in-memory cache next to storage on disk.
Exemption When the cache fills up, which data is to be removed so that newly fetched pages can be stored?
Sharing Does each browser make use of a private cache, or is a cache to be shared among browsers of
different users?
Refreshing When does a browser check if cached data is still up-to-date?
Design Goals
• Being scalable
1. Size scalability
• A familiar scenario
• A service is implemented on a single machine can provide bottlenecks
• Computational capacity
• Storage capacity and I/O transfer rate
• Network between user and provider
2. Geographical scalability
3. Administrative scalability
Fallacies of Distributed Computing
• The network is reliable
• Latency is zero
• Bandwidth is infinite
• The network is secure
• Topology doesn’t change
• There is one administrator
• Transport cost is zero
• The network is homogeneous