A Multicast Discovery Protocol To Locate Services On A Local

Network Our research aims at providing a scalable, reliable, and robust approach for web service discovery. An overview of web service discovery. Service-oriented Computing (SOC) is emerging as a new paradigm for developing distributed applications. Service discovery, among the most fundamental elements of SOC, is critical to the success of SOC as a whole. Traditional service discovery approaches of the web services technology are based on Universal Description, Discovery, and Integration (UDDI). Centralized service registries used by UDDI may easily suffer from problems such as performance bottleneck and vulnerability to failures as the number of service consumers and requests increase in an open SOC environment. This inherent disadvantage prevents web services from being applied in large scalable service networks. As SOC environment is largely distributed, a decentralized approach appears to be the most natural way to address the above issues and achieve scalable, reliable and robust service discovery. Service-Oriented Computing (SOC) is emerging as a paradigm for developing distributed applications. A critical issue of utilizing SOC is to have a scalable, reliable, and robust service discovery mechanism. Traditional service discovery methods using centralized registries can easily suffer from problems such as performance bottleneck and vulnerability to failures in large scalable service networks, thus functioning abnormally. To address these problems, this paper proposes a peer-to-peer-based decentralized service discovery approach named Chord4S. Chord4S utilizes the data distribution and lookup capabilities of the popular Chord to distribute and discover services in a decentralized manner. A P2P-based decentralized service discovery approach consists of a set of distributed nodes that form a structured P2P overlay network. Upon registration, the description of a service is distributed to a relevant node to be stored in its repository. A service query can be submitted to any node, and this node, if does not store the required service description, is able to route the query to an appropriate node for resolution. Descriptions of matched services are retrieved and returned to the service consumer as the result of the query.