A QoS Broker Based Architecture for Dynamic Web Service Selection

QoS-Based Architecture for Discovery and Selection of suitable Web Services Using Non-functional properties

“…Web Services (WSs) are segmental, self-defining, and slackly coupled software applications that can be publicized, found, and used across the Internet using a set of standards such as SOAP, WSDL, and UDDI [1]. It can be accessed over the network through the standardized XML messages.…”

QoS Broker based Architecture for Dynamic Web Service Discovery and Composition

“…The limitation with the proposed architecture is that only one of the QoS parameters is considered during composition and selection of optimal path. A web service discovery architecture is presented that contains two additional components with the traditional service discovery model, which are QoS registry to store the QoS information and QoS broker to facilitate web service discovery [16][17]. The QoS broker registers and edits the web service QoS property values through the QoS registry.…”

“…First, focus is given on the selection of service providers rather than on services to be composed [16][17]. Second, non-functional information published by the service providers may not always be trustworthy [16][17]31]. Third, most of clients are not experienced enough to acquire the best selection of web service based on its described QoS characteristics [7,31].…”

“…First, focus is given on the selection of service providers rather than on services to be composed [16][17]. Second, non-functional information published by the service providers may not always be trustworthy [16][17]31].…”

WSARCH: Uma arquitetura para a provisão de web services com qualidade de serviço

“…Como se trata de uma tecnologia que envolve diversos conceitos e aplicações de sistemas distribuídos, se faz necessária uma análise de problemas como disponibilidade, dependência e confiabilidade de Web Services, além da qualidade de serviço envolvida na comunicação das aplicações orientadas a serviços (não muito explorada pelos órgãos responsáveis pela padronização da tecnologia de Web Services). Alguns trabalhos (Chen et al, 2003), (Ludwig, 2003), (Wu et al, 2003), (Erradi e Maheshwari, 2005), (Tsai et al, 2006), (Badidi et al, 2006), (Tavares e Westphall, 2006), (D'Mello et al, 2008), (Zhao e Tan, 2009), tratam desses problemas com a proposição de arquiteturas isoladas. Assim, não se preocupam em considerar a possibilidade de utilização de recursos computacionais ociosos, que poderiam ser aproveitados para a execução de Web Services num ambiente globalmente distribuído.…”