Social cloud computing: Difference between revisions

Content deleted Content added
Lars1298 (talk | contribs)
Lars1298 (talk | contribs)
Line 12:
1) Availability of Computational Resources
 
In the case of traditional cloud computing, availability on demand is essential for many cloud customers. Social Cloud Computing doesn't provide this availability guarantee because in a P2P environment, peers are usually those using only mobile devices and theywhich may enter or leave the P2P network at any time, or PCs which have a primary purpose that can override the P2P computation at any time. The only relatively successful use cases as of recent years are those which do not require real time results, only computation power for a small subset or module of a larger algorithm or data set.
 
2) Trust and Security
 
Unlike large scale data centers and company brand image, people may be less likely to trust peers vs. a large company like Google or Amazon. Running some sort of computation with sensitive information would then need to be encrypted properly and the overhead of that encryption may renderreduce the usefulness of the productP2P minimaloffloading. When resources are distributed in small pieces to many peoplepeers for computations, inherent trust must be placed in the client, regardless of the encryption that may be promised to the client.
 
3) Reliability
 
Similar to availability, reliability of computations must be consistent and uniform. If computations offloaded to the client are continuously interrupted, some mechanism for detecting this must be in place such that the client may know the computation is tainted or needs to be completely re-run. In P2P social computing, reliable expected computation power is difficult to achieve because the speed of the client calculation may depend on how much the client is using the end device. Some ways of overcoming this ismay be to only allow computations to occur at night, or during specified times the client resources will not be in use.
 
==See also==