One of the major current trends in serviceoriented systems is the emphasis given to the need of introducingruntime adaptation features, so that the system can meet its QoS requirements in a volatile operating environment. In this paper we present the design and implementation of a service roker that supports the QoS-driven runtime adaptation of SOA applications offered as composite services to users. We describe the functionalities provided by the broker components and present their design and implementation according to two different versions we have developed and that are both based on open source products. The components of the first version have been developed in Java as Web services, while the second version takes advantage of OpenESB. Since the broker needs to sustain a traffic of requests generated by several concurrent users, we also present the replicated architectures of the two broker versions. We discuss the design tradeoffs and the lesson we have learned in developing the broker. © 2010 IEEE.
Cardellini, V., Iannucci, S. (2010). Designing a broker for QoS-driven runtime adaptation of SOA applications. In ICWS 2010 - 2010 IEEE 8th International Conference on Web Services (pp.504-511) [10.1109/ICWS.2010.77].
Designing a broker for QoS-driven runtime adaptation of SOA applications
Iannucci S.
2010-01-01
Abstract
One of the major current trends in serviceoriented systems is the emphasis given to the need of introducingruntime adaptation features, so that the system can meet its QoS requirements in a volatile operating environment. In this paper we present the design and implementation of a service roker that supports the QoS-driven runtime adaptation of SOA applications offered as composite services to users. We describe the functionalities provided by the broker components and present their design and implementation according to two different versions we have developed and that are both based on open source products. The components of the first version have been developed in Java as Web services, while the second version takes advantage of OpenESB. Since the broker needs to sustain a traffic of requests generated by several concurrent users, we also present the replicated architectures of the two broker versions. We discuss the design tradeoffs and the lesson we have learned in developing the broker. © 2010 IEEE.I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.