View article

In any critical system, high‐availability of software components like web services has so far been achieved through replication. Three replication strategies known as active, passive, and hybrid, describe for example how many replicas are needed, where to locate replicas, and how replicas interact with the original web service and among themselves if needed. The purpose of this paper is to show how replicates could be substituted with components that are similarly functional to the component that needs back‐up in case of failure.

After examination of the different existing replication strategies, it was decided to test the suitability of the proposed web services high‐availability approach based on communities for each strategy. To this end, the specification of web services using two behaviors, namely control and operational, was deemed appropriate.

The active …