First, thanks to a smaller number of replicas each transaction needs to atomically update in a cluster, the protocol significantly reduces the transaction abort rate, which tends to soar in large transactional systems. Third, read-only queries have the flexibility to see database views of different degrees of consistency and data currency. This ranges from global, most up to date, and consistent views, to local, consistent, but potentially old views, to local, nearest to users but potentially inconsistent views. Fourth, the protocol maintains its scalability by allowing dynamic system reconfiguration as it grows by splitting a cluster into two or more smaller ones. Fifth, autonomy of the clusters is preserved as no specific protocol is required to update replicas within the same cluster.
Clusters are, therefore, free to use any valid replication or concurrency control protocols.
Permission to make digital or hard copies is granted provided that copies are not made or distributed for profit or direct commercial advantage, and that copies show this notice on the first page or initial screen of a display along with the full citation. Maintaining Availability in Partitioned Replicated Databases. A Position Statement for Managing Replicated Data. Increasing Availability Under Mutual Exclusion Constraints with Dynamic Vote Reassignment. Dynamic Hierarchical Caching for Large-Scale Distributed File Systems.