GlueQoS: middleware to sweeten quality-of-service policy interactions

@inproceedings{Wohlstadter04, abstract = {A holy grail of component-based software engineering is write-once, reuse everywhere. However, in modern distributed, component-based systems supporting emerging application areas such as service-oriented e-business (where Web services are viewed as components) and peer-to-peer computing, this is difficult. Non-functional requirements (related to quality-of-service (QoS) issues such as security, reliability, and performance) vary with deployment context, and sometimes even at run-time, complicating the task of re-using components. In this paper, we present a middleware-based approach to managing dynamically changing QoS requirements of components. Policies are used to advertise non-functional capabilities and vary at run-time with operating conditions. We also provide middleware enhancements to match, interpret, and mediate QoS requirements of clients and servers at deployment time and/or runtime.}, author = {Wohlstadter, E. and Tai, S. and Mikalsen, T. and Rouvellou, I. and Devanbu, P.}, citeulike-article-id = {382662}, journal = {Software Engineering, 2004. ICSE 2004. Proceedings. 26th International Conference on}, pages = {189--199}, posted-at = {2008-09-07 22:46:09}, priority = {2}, title = {GlueQoS: middleware to sweeten quality-of-service policy interactions}, url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1317441}, year = {2004} }

TY - CONF ID - Wohlstadter04 L3 - citeulike-article-id:382662 N2 - A holy grail of component-based software engineering is write-once, reuse everywhere. However, in modern distributed, component-based systems supporting emerging application areas such as service-oriented e-business (where Web services are viewed as components) and peer-to-peer computing, this is difficult. Non-functional requirements (related to quality-of-service (QoS) issues such as security, reliability, and performance) vary with deployment context, and sometimes even at run-time, complicating the task of re-using components. In this paper, we present a middleware-based approach to managing dynamically changing QoS requirements of components. Policies are used to advertise non-functional capabilities and vary at run-time with operating conditions. We also provide middleware enhancements to match, interpret, and mediate QoS requirements of clients and servers at deployment time and/or runtime. JF - Software Engineering, 2004. ICSE 2004. Proceedings. 26th International Conference on EP - 199 TI - GlueQoS: middleware to sweeten quality-of-service policy interactions SP - 189 AU - Wohlstadter, E AU - Tai, S AU - Mikalsen, T AU - Rouvellou, I AU - Devanbu, P PY - 2004/// UR - http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1317441 ER -