Title:
Autonomic Information Flows

dc.contributor.author Schwan, Karsten
dc.contributor.author Cooper, Brian F.
dc.contributor.author Eisenhauer, Greg S.
dc.contributor.author Gavrilovska, Ada
dc.contributor.author Wolf, Matthew
dc.contributor.author Abbasi, Hasan
dc.contributor.author Agarwala, Sandip
dc.contributor.author Cai, Zhongtang
dc.contributor.author Kumar, Vibhore
dc.contributor.author Lofstead, Jay
dc.contributor.author Mansour, Mohamed S.
dc.contributor.author Seshasayee, Balasubramanian
dc.contributor.author Widener, Patrick M. (Patrick McCall)
dc.date.accessioned 2006-02-07T20:18:56Z
dc.date.available 2006-02-07T20:18:56Z
dc.date.issued 2005
dc.description.abstract Today's enterprise systems and applications implement functionality that is critical to the ability of society to function. These complex distributed applications, therefore, must meet dynamic criticality objectives even when running on shared heterogeneous and dynamic computational and communication infrastructures. Focusing on the broad class of applications structured as distributed information flows, the premise of our research is that it is difficult, if not impossible, to meet their dynamic service requirements unless these applications exhibit autonomic or self-adjusting behaviors that are `vertically' integrated with underlying distributed systems and hardware. Namely, their autonomic functionality should extend beyond the dynamic load balancing or request routing explored in current web-based software infrastructures to (1) exploit the ability of middleware or systems to be aware of underlying resource availabilities, (2) dynamically and jointly adjust the behaviors of interacting elements of the software stack being used, and even (3) dynamically extend distributed platforms with enterprise functionality (e.g., network-level business rules for data routing and distribution). The resulting vertically integrated systems can meet stringent criticality or performance requirements, reduce potentially conflicting behaviors across applications, middleware, systems, and resources, and prevent breaches of the `performance firewalls' that isolate critical from non-critical applications. This paper uses representative information flow applications to argue the importance of vertical integration for meeting criticality requirements. This is followed by a description of the AutoFlow middleware, which offers methods that drive the control of application services with runtime knowledge of current resource behavior. Finally, we demonstrate the opportunities derived from the additional ability of AutoFlow to enhance such methods by also dynamically extending and controlling the underlying software stack, first to better understand its behavior and second, to dynamically customize it to better meet current criticality requirements. en
dc.format.extent 1001052 bytes
dc.format.mimetype application/pdf
dc.identifier.uri http://hdl.handle.net/1853/7714
dc.language.iso en_US en
dc.publisher Georgia Institute of Technology en
dc.relation.ispartofseries CERCS;GIT-CERCS-05-22 en
dc.subject AutoFlow
dc.subject Conflicting behaviors across applications
dc.subject Criticality requirements
dc.subject Distributed applications
dc.subject Middleware
dc.subject Self-adjusting behaviors
dc.subject Software stack management
dc.subject Vertical integration
dc.title Autonomic Information Flows en
dc.type Text
dc.type.genre Technical Report
dspace.entity.type Publication
local.contributor.author Gavrilovska, Ada
local.contributor.author Schwan, Karsten
local.contributor.corporatename Center for Experimental Research in Computer Systems
local.relation.ispartofseries CERCS Technical Report Series
relation.isAuthorOfPublication 74b4106d-3b1c-40a5-993e-dea3eecbdba3
relation.isAuthorOfPublication a89a7e85-7f70-4eee-a49a-5090d7e88ce6
relation.isOrgUnitOfPublication 1dd858c0-be27-47fd-873d-208407cf0794
relation.isSeriesOfPublication bc21f6b3-4b86-4b92-8b66-d65d59e12c54
Files
Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
git-cercs-05-22.pdf
Size:
977.59 KB
Format:
Adobe Portable Document Format
Description:
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.86 KB
Format:
Item-specific license agreed upon to submission
Description: