Requirements of a Recovery Solution for Failure of Composite Web Services
Hadi Saboohi, Sameem Abdul Kareem

TL;DR
This paper reviews failure causes in composite web services and explores the essential requirements for effective recovery solutions to enhance system robustness and minimize delays during failure handling.
Contribution
It systematically analyzes failure reasons and identifies key requirements for designing effective recovery solutions for composite web services.
Findings
Failure causes of composite web services are categorized.
Key requirements for recovery solutions are identified.
Emphasis on minimizing delay during failure recovery.
Abstract
Web services are building blocks of interoperable systems. Composing Web services makes the processes capable of doing complex tasks. Composite services may fail during their execution which can be diagnosed by a mediator. The mediator adapts the structure so that the failure is recovered. Moreover, future executions should avoid the situation or organize a strategy to repair the structure with a minimum delay. In this paper the failure reasons of a composite service are reviewed. Furthermore, the requirements of a solution for recovery of a system from a failure are investigated.
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
