A critique of ANSI SQL isolation levels
SIGMOD '95 Proceedings of the 1995 ACM SIGMOD international conference on Management of data
Fault-tolerant broadcasts and related problems
Distributed systems (2nd Ed.)
Group communication specifications: a comprehensive study
ACM Computing Surveys (CSUR)
Database Replication Techniques: A Three Parameter Classification
SRDS '00 Proceedings of the 19th IEEE Symposium on Reliable Distributed Systems
Protocol Switching: Exploiting Meta-Properties
ICDCSW '01 Proceedings of the 21st International Conference on Distributed Computing Systems
Comparison of Database Replication Techniques Based on Total Order Broadcast
IEEE Transactions on Knowledge and Data Engineering
Middleware based data replication providing snapshot isolation
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Managing Transaction Conflicts in Middleware-based Database Replication Architectures
SRDS '06 Proceedings of the 25th IEEE Symposium on Reliable Distributed Systems
Run-time switching between total order algorithms
Euro-Par'06 Proceedings of the 12th international conference on Parallel Processing
MADIS: a slim middleware for database replication
Euro-Par'05 Proceedings of the 11th international Euro-Par conference on Parallel Processing
Managing multiple isolation levels in middleware database replication protocols
ISPA'06 Proceedings of the 4th international conference on Parallel and Distributed Processing and Applications
Supporting multiple isolation levels in replicated environments
Data & Knowledge Engineering
| Hi-index | 0.00 |
Database replication tasks are accomplished with the aid of consistency protocols. Commonly, proposed solutions use a single replication protocol providing just one isolation level. The main drawback of this approach is its lack of flexibility for changing scenarios -i.e. workloads, access patterns...- or heterogeneous client application requirements. This work proposes a metaprotocol for supporting several replication protocols which use different replication techniques or provide different isolation levels. With this metaprotocol, replication protocols can either work concurrently with the same data or be sequenced for adapting to changing environments. In this line, the use of a load monitor would enable the best choice for each transaction, selecting the most appropriate protocol according to the current system characteristics. This paper is focused on outlining this metaprotocol design, establishing the metadata set needed and the required interaction between the main database replication protocol families.