Abstract
In this paper we present a Service Injection and composition De sign Pattern for Unstructured Peer -to-Peer networks, which is designed with Aspect -oriented design patterns, and amalgamation of the Strategy, Worker Object, and Check -List Design Patterns used to design the Self -Adaptive Systems. It will apply selfreconfiguration planes dynamically without the interruption or intervention of the administrator for handling service failures at the servers. When a client requests for a complex service, Service Composition should be done to fulfil the request. If a service is not available in the memory, it will be injected as Aspectual Feature Module code.We used Service Oriented Architecture (SOA) with Web Services in Java to Implement the composite Design Pattern. As far as we know, there are no studies on composition of design patterns for Peer-to-peer computing domain. The pattern is described using a java -like notation for the classes and interfaces. A simple UML class and Sequence diagrams are depicted.
Highlights
The most widely focused elements of the autonomic computing systems are self-* properties
In our design pattern we have provided the capabilities of Web Services Composition[4], Service Invocation, and Inclusion of the new Service Operation as a Feature Module, all the three are provided in each and every server in a Distributed Application
Initially the client system will request for the Web Service Description Language (WSDL) from all the service providing servers, when the client request for a complex task that need to be fulfilled by more than two service combinations
Summary
The most widely focused elements of the autonomic computing systems are self-* properties. For a system to be self-manageable they should be self-configuring, self-healing, self-optimizing, self-protecting and they have to exhibit self-awareness, self-situation and self-monitoring properties [2]. As the web continues to grow in terms of content and the number of connected devices, peer-to-peer computing is becoming increasingly prevalent. Some of the popular examples are file sharing, distributed computing, and instant messenger services. Each one of them provides different services, but shares the same mechanism like Discovery of peers, searching, file and data transfer. Developed peer-to-peer applications are inefficient with the developers solving the same problems and duplicating the similar infrastructure implementations [15]. Most of the applications are specific to a single platform and can't communicate and share data with different applications
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
