2015
DOI: 10.1007/s11280-015-0329-1
|View full text |Cite
|
Sign up to set email alerts
|

Modeling dynamic recovery strategy for composite web services execution

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
14
0
1

Year Published

2017
2017
2023
2023

Publication Types

Select...
4
2
2

Relationship

1
7

Authors

Journals

citations
Cited by 27 publications
(15 citation statements)
references
References 26 publications
0
14
0
1
Order By: Relevance
“…Although, many solutions have been proposed to adapt a web services based software solution to QoS changes of its component web services [20,21], but runtime monitoring of component web services, and then communication of the data, collected during monitoring, to the clients still needs to improve.…”
Section: Related Workmentioning
confidence: 99%
“…Although, many solutions have been proposed to adapt a web services based software solution to QoS changes of its component web services [20,21], but runtime monitoring of component web services, and then communication of the data, collected during monitoring, to the clients still needs to improve.…”
Section: Related Workmentioning
confidence: 99%
“…If the faulty component service can be retried [24], replicated [25], or substituted [26], forward recovery is allowed. If the effects produced by the faulty component service need to be compensated [27], backward recovery is allowed [28]. However, users need to wait a long time to get the desired response when forward recovery is adopted, and users are unable to get the desired answer to their queries when backward recovery is adopted [29].…”
Section: Dynamic Fault Tolerance Strategiesmentioning
confidence: 99%
“…Current execution state and partial results are taken as a snapshot, which is returned to the user when a fault occurs. The checkpointed composite service can be restarted from the latest saved state, and the aggregated transactional attributes are not affected [28]. The recent researches of the dynamic fault tolerance are discussed in the following sections.…”
Section: Dynamic Fault Tolerance Strategiesmentioning
confidence: 99%
“…12,53,54 For example, if a service is pr or cr, several replicas can be simultaneously invoked or it can be replaced by another functionally equivalent service when it fails. Some approaches have proposed some techniques, such as replication and substitution, that can support the condition of 100% of successful execution.…”
Section: Transactional Properties For Non-composite Servicesmentioning
confidence: 99%