WebOS, PlanetLab, Starfish: Difference between revisions

From Soma-notes
No edit summary
 
Rhooper (talk | contribs)
Line 8: Line 8:


[http://homeostasis.scs.carleton.ca/~soma/distos/2008-03-17/anderson-planetlab-learning.pdf Thomas Anderson and Timothy Roscoe, "Learning from PlanetLab" (2006)]
[http://homeostasis.scs.carleton.ca/~soma/distos/2008-03-17/anderson-planetlab-learning.pdf Thomas Anderson and Timothy Roscoe, "Learning from PlanetLab" (2006)]
----
=== WebOS ===
==== Key features ====
* High Availability
* Lower Latency
* Fault Tolerance
Consensus: WebOS isn't really an distributed OS
==== Main components ====
* Smart Client
* WebFS
* Global naming scheme based on URLs
* Process control system
* CRISIS authentication/authorization system (Certificates with ACLs)
==== Key ideas that were/were not not adopted from WebFS ====
Adopted:
* General idea of wide area dynamic distribution -> Akamai (but primarily for static content)
* Global naming using URLs
Not Adopted:
* CRISIS
* WebFS (Although WebDAV could be said to be related)
* Smart client (for web sites)
==== What are the pros and cons of using smart clients to do load balancing? ====
Pro:
* Distributes computation
* More flexible
Con:
* Vulnerable to Denial of Service or other forms of attacks
* Extra network overhead to locate a service

Revision as of 23:07, 18 March 2008

Readings

Amin Vahat et al., "WebOS: Operating System Services for Wide Area Applications" (1998)

Adnan Agbaria and Roy Friedman, "Starfish: Fault-Tolerant Dynamic MPI Programs on Clusters of Workstations" (2003)

Larry Peterson et al., "Experiences Building PlanetLab" (2006)

Thomas Anderson and Timothy Roscoe, "Learning from PlanetLab" (2006)




WebOS

Key features

  • High Availability
  • Lower Latency
  • Fault Tolerance

Consensus: WebOS isn't really an distributed OS

Main components

  • Smart Client
  • WebFS
  • Global naming scheme based on URLs
  • Process control system
  • CRISIS authentication/authorization system (Certificates with ACLs)

Key ideas that were/were not not adopted from WebFS

Adopted:

  • General idea of wide area dynamic distribution -> Akamai (but primarily for static content)
  • Global naming using URLs

Not Adopted:

  • CRISIS
  • WebFS (Although WebDAV could be said to be related)
  • Smart client (for web sites)

What are the pros and cons of using smart clients to do load balancing?

Pro:

  • Distributes computation
  • More flexible

Con:

  • Vulnerable to Denial of Service or other forms of attacks
  • Extra network overhead to locate a service