| A. Fox. A Framework for Separating Server Scalability and Availability from Internet Application Functionality. PhD thesis, U.C.Berkeley, 1998. |
....the service level path to instantiate the services as well as the no op services as required. Since in our architecture, each overlay node is a service cluster, we focus on load balancing across service clusters. There has been past research in load balancing across machines within a cluster [11], 12] and we leverage on this. Thus, in abstract terms, we have a graph that represents an overlay network. Each node in the graph has a set of services. We assume that the set of locations for each kind of service is known globally (this is similar to the knowledge of the set of mirrors for a ....
A. Fox, A Framework for Separating Server Scalability and Availability from Internet Application Functionality, Ph.D. thesis, U.C.Berkeley, 1998.
....the service level path to instantiate the services as well as the no op services as required. Since in our architecture, each overlay node is a service cluster, we focus on load balancing across service clusters. There has been past research in load balancing across machines within a cluster [11], 12] and we leverage on this. Thus, in abstract terms, we have a graph that represents an overlay network. Each node in the graph has a set of services. We assume that the set of locations for each kind of service is known globally (this is similar to the knowledge of the set of mirrors for a ....
A. Fox, "A Framework for Separating Server Scalability and Availability from Internet Application Functionality," Ph.D. dissertation, U.C.Berkeley, 1998.
....operating costs while maintaining a satisfactory quality of service to users. We want large scale Internet services to resemble power plants not only do they need to scale, but they should also be highly automated and manageable by people without much knowledge of the underlying circuitry [59]. The chores today s administrators face, such as monitoring system health and moving data around to balance system load, should be delegated to the software itself; people should be responsible only for occasionally replacing broken parts and adding nodes or disks as system demand grows. Such a ....
Armando Fox. A Framework for Separating Server Scalability and Availability from Internet Application Functionality. PhD thesis, UC Berkeley, 1998. 1
....nodes in the system, is easy to manage as the system is self con guring with regard to load and node con guration, and is available even when some of its nodes fail. Similar strategies have been used in other cluster based systems to build highly scalable le systems [2, 79] and Internet services [23, 24]. 2.2 Classi cation We now develop four categories to describe and compare systems that manage distributed state. The four categories are application programming interface (API) guarantees, strategy, and assumptions. These categories capture the external speci cation of a system (API and ....
Armando Fox. A Framework for Separating Server Scalability and Availability from Internet Application Functionality. PhD thesis, University of California at Berkeley, 1998.
....or completely orthogonalized. This allows the designers to focus on exposing the aggregate functionality to the user, leaving the details of manipulating applications component references to the middleware. Benefits of such partial or complete orthogonalization of layers is described in [7]. But, the remaining question is, how might we implement such layering in this domain 1 We call our framework components services to contrast with the more generic term objects. A service is any entity that can be invoked over the Internet using a known messaging format. Thus, a web server ....
Armando Fox. A Framework for Separating Server Scalability and Availability from Internet Application Functionality. PhD thesis, University of California, Berkeley, 1998.
No context found.
A. Fox. A Framework for Separating Server Scalability and Availability from Internet Application Functionality. PhD thesis, U.C.Berkeley, 1998.
No context found.
A. Fox. A Framework for Separating Server Scalability and Availability from Internet Application Functionality. PhD thesis, U.C.Berkeley, 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC