Abstract
During the execution of a Composite Web Service (CWS), different faults may occur and cause a Web Service (WS) to fail. To repair failures some strategies can be applied, such as WS retry or substitution, compensation of the performed execution, roll-back, replication, or take checkpoints to later restart the execution. Each strategy has advantages and disadvantages on different execution scenarios and can produce different impact on the CWS QoS, depending on the execution environment and execution state at the moment of the failure. In this paper we propose a model and show experimental results to dynamically decide which recovery strategy is the best choice in terms of the impact on the CWS QoS.
Sign-in/Register to access full text options 
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.
