Learn More
To deal with consistency in replicated database systems, particularities of the chosen target environment and applications must be considered. To this end, several replication protocols have been discussed in the literature, each one requiring a different set of data to be maintained for each replicated object or for each transaction being executed. For(More)
  • F. D. Muñoz-Escoı, J. Pla-Civera, +4 authors J. R. González de Mendı́vil
Database replication protocols need to detect, block or abort part of conflicting transactions. A possible solution is to check their writesets (and also their readsets in case a serialisable isolation level is requested), which burdens the consumption of CPU time. This gets even worse when the repli-cation support is provided by a middleware, since there(More)
Current database replication protocols take care of read-write and/or write-write conflict evaluation. If there are no such conflicts, protocols send transactions to the database and assume they will eventually commit. But commitment may fail due to integrity constraints violations. Also, new conflicts may arise as a result of the integrity checking(More)
The availability of information systems benefits from distributed replication. Different applications and users require different degrees of data availability, consistency and integrity. The latter are perceived as competing objectives that need to be reconciled by appropriate replication strategies. We outline work in progress on a replication architecture(More)
  • 1