SLA-driven distributed application development

Vinod Muthusamy, Hans Arno Jacobsen

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

3 Scopus citations

Abstract

The management of Service Level Agreements (SLA) in the development of business processes in a Service Oriented Architecture (SOA) often requires much manual and errorprone effort by all parties throughout the lifecycle of the processes. The formal specification of SLAs into development tools can simplify some of this effort. In particular, the runtime provisioning and monitoring of processes can be achieved by an autonomic system that adapts to changing conditions to maintain the SLA's goals. A cost model allows the efficient execution and monitoring of processes, based on a declarative, user-specified optimality function. Experiments demonstrate that the system can indeed adapt to changing workload conditions, saving roughly 70% of the network bandwidth in one particular experiment.

Original languageEnglish
Title of host publicationProceedings of the 3rd Workshop on Middleware for Service Oriented Computing, MW4SOC 2008 - Held at the ACM/IFIP/USENIX International Middleware Conference
PublisherAssociation for Computing Machinery, Inc
Pages31-36
Number of pages6
ISBN (Electronic)9781605583686
DOIs
StatePublished - 1 Dec 2008
Externally publishedYes
Event3rd Workshop on Middleware for Service Oriented Computing, MW4SOC 2008 - Leuven, Belgium
Duration: 1 Dec 20085 Dec 2008

Publication series

NameProceedings of the 3rd Workshop on Middleware for Service Oriented Computing, MW4SOC 2008 - Held at the ACM/IFIP/USENIX International Middleware Conference

Conference

Conference3rd Workshop on Middleware for Service Oriented Computing, MW4SOC 2008
Country/TerritoryBelgium
CityLeuven
Period1/12/085/12/08

Keywords

  • Service level agreement
  • Service oriented architecture

Fingerprint

Dive into the research topics of 'SLA-driven distributed application development'. Together they form a unique fingerprint.

Cite this