Modeling Snapshot of Composite WS Execution by Colored Petri Nets

Cardinale, Yudith; Rukoz, Marta; Angarita, Rafael

doi:10.1007/978-3-642-45263-5_2

Cited by 4 publications

(6 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Based on Coloured Petri-Nets, a checkpoint approach is proposed in [46]. If a fault occurs, the approach relaxes the all-or-nothing attribute by executing a transactional composite Web service as much as possible and taking a snapshot of faulted state.…”

Section: Checkpointmentioning

confidence: 99%

Overview on Fault Tolerance Strategies of Composite Service in Service Computing

Zhang

Zhou

Sun

et al. 2018

Wireless Communications and Mobile Computing

View full text Add to dashboard Cite

In order to build highly reliable composite service via Service Oriented Architecture (SOA) in the Mobile Fog Computing environment, various fault tolerance strategies have been widely studied and got notable achievements. In this paper, we provide a comprehensive overview of key fault tolerance strategies. Firstly, fault tolerance strategies are categorized into static and dynamic fault tolerance according to the phase of their adoption. Secondly, we review various static fault tolerance strategies. Then, dynamic fault tolerance implementation mechanisms are analyzed. Finally, main challenges confronted by fault tolerance for composite service are reviewed.

show abstract

Section: Checkpointmentioning

confidence: 99%

Overview on Fault Tolerance Strategies of Composite Service in Service Computing

Zhang

Zhou

Sun

et al. 2018

Wireless Communications and Mobile Computing

View full text Add to dashboard Cite

show abstract

“…6,14 With this approach, relaxing atomicity means that instead of "all-or-nothing," users can have an "all-something-or-nothing" property. 6,14 With this approach, relaxing atomicity means that instead of "all-or-nothing," users can have an "all-something-or-nothing" property.…”

Section: Relaxing Atomicity By Checkpointingmentioning

confidence: 99%

“…[4][5][6][7] Traditional ACID transaction model provides an "all-or-nothing" execution approach to support service failures generally based on transactional properties, compensation, rollback, and replication. The constantly increasing number of such services for accessing data on the cloud arises new challenges for enabling their integration and collaboration while guarantying self-organization and self-adaptivity properties, specially to manage failures.…”

Section: Introductionmentioning

confidence: 99%

“…() Meanwhile, transactional support is a way to guarantee reliable composite service (CS), by considering the classical ACID (atomicity, consistency, isolation, and durability) transactional properties or a variation of them. ()…”

Section: Introductionmentioning

confidence: 99%

“…2,3 Meanwhile, transactional support is a way to guarantee reliable composite service (CS), by considering the classical ACID (atomicity, consistency, isolation, and durability) transactional properties or a variation of them. [4][5][6][7] Traditional ACID transaction model provides an "all-or-nothing" execution approach to support service failures generally based on transactional properties, compensation, rollback, and replication. However, for some applications, the classical "all-or-nothing" model is too restrictive for independent and multi-proprietors services running on distributed environments, such as cloud platforms.…”

mentioning

confidence: 99%

See 2 more Smart Citations

Fuzzy ACID properties for self‐adaptive composite cloud services execution

Cardinale

Haddad

Manouvrier

et al. 2017

Concurrency and Computation

Self Cite

View full text Add to dashboard Cite

The ACID transaction model has played a cornerstone role in service composition to guarantee that composite services (CSs) have transactional support and consistent outcomes even in presence of failures. However, the classical ACID properties are too restrictive for independent and multi-proprietors services running on distributed environments, such clouds. Transactional properties allow a relaxed atomicity and isolation, providing an "all-or-(almost)nothing" model.In previous works, we proposed a model to relax atomicity, called fuzzy atomicity, according user requirements (acceptable fuzzy atomicity). In this article, we extend that model and propose an approach to measure the fuzzy atomicity. Our model allows to self-adapt the CS execution, taking into account the state of the CS execution and user preferences (ie, the acceptable fuzzy atomicity expressed in the user requirements). This fuzzy atomicity measure is applied in a self-adaptive CS execution model based on the transactional properties (pivot, compensatable, and retriable) of its component services and on a checkpointing mechanism. It is suitable to cloud computing, which offers cloud services on demand and in which CS execution should preserve the self-organizing and self-adaptivity properties of such environment, specially in the presence of failures. We show how it is possible to relax the retriable property in CSs execution, based on our fuzzy atomicity model. Additionally, in this work, we present a comparative analysis of the most recent works in the context of ACID properties relaxation for CS. KEYWORDScloud computing services, fault tolerance, relaxed atomicity, self-adaptive execution, service composition INTRODUCTIONCloud is the most flexible and affordable on-demand platform for deploying custom applications in the form of services that are commonly called cloud services. The constantly increasing number of such services for accessing data on the cloud arises new challenges for enabling their integration and collaboration while guarantying self-organization and self-adaptivity properties, specially to manage failures. 1 Cloud services composition is a way to reach this collaboration and integration, since it consists in combining and coordinating several services allowing more complex service functionality that can respond more complex user queries. 2,3 Meanwhile, transactional support is a way to guarantee reliable composite service (CS), by considering the classical ACID (atomicity, consistency, isolation, and durability) transactional properties or a variation of them. [4][5][6][7] Traditional ACID transaction model provides an "all-or-nothing" execution approach to support service failures generally based on transactional properties, compensation, rollback, and replication. However, for some applications, the classical "all-or-nothing" model is too restrictive for independent and multi-proprietors services running on distributed environments, such as cloud platforms. In this sense, advanced transactional models have been adapted to rel...

show abstract