
In this paper, the software rejuvenation model, designed for a continuously running non-replicated application, is extended for the case of distributed systems with rejuvenated replicated services. It identifies to which extent an increase in availability can be achieved and how the cost associated with downtime can be reduced using software rejuvenation combined with replication. Based on two representative situations in a case study, it can be concluded that replica rejuvenation improves the service availability and reduces the cost associated with downtime. In general, replica rejuvenation improves the availability even in the cases where, in the original model, rejuvenation is not recommended.
| citations This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
