Fulfillment of the requirements

Main points:

Asynchrony

• Operations have an identity (instances), and thus may be notified asynchronously, and thus kept up-to-date. This way, their advertised behaviour may be kept deterministic
• Because of determinism, there is no penalty in performance or availability at the time of use, i.e. for the clients. The impact of distribution is smoothed.
• Early detection of conflicts, due to the registration of operations at the resources (advantages of "optimistic locking" without the inconvenients)
• Asynchronous notifications allow for local copies for efficiency, or duplication for fault-tolerance

Typing and composition

• Operations offer an arbitrarily fine granularity, and semantics to minimize the actual conflicts. This enhances availability and efficiency
• Chains of Initiator/Operations links ensure that there is no semantic loss, e.g. for conflict resolution, and thus support scalability
• If the operations are specialized for the actual resources, the conflict detection can be done locally, but the arbitration may access information from the ultimate initiators, and thus decrease the impacts of eventual (often partial) roll-backs

Table of contents