Understanding the limitations of causally and totally ordered communication
SOSP '93 Proceedings of the fourteenth ACM symposium on Operating systems principles
From group communication to transactions in distributed systems
Communications of the ACM
Consistent object replication in the eternal system
Theory and Practice of Object Systems - Special issue high availability in CORBA
Implementing E-Transactions with Asynchronous Replication
IEEE Transactions on Parallel and Distributed Systems
Software fault tolerance techniques and implementation
Software fault tolerance techniques and implementation
Distributed Systems: Principles and Paradigms
Distributed Systems: Principles and Paradigms
Transaction Processing: Concepts and Techniques
Transaction Processing: Concepts and Techniques
EDCC-2 Proceedings of the Second European Dependable Computing Conference on Dependable Computing
Reconciling Replication and Transactions for the End-to-End Reliability of CORBA Applications
On the Move to Meaningful Internet Systems, 2002 - DOA/CoopIS/ODBASE 2002 Confederated International Conferences DOA, CoopIS and ODBASE 2002
Integrating Group Communication with Transactions for Implementing Persistent Replicated Objects
Advances in Distributed Systems, Advanced Distributed Computing: From Algorithms to Systems
CORBA Fault-Tolerance: Why It Does Not Add Up
FTDCS '99 Proceedings of the 7th IEEE Workshop on Future Trends of Distributed Computing Systems
Unification of Replication and Transaction Processing in Three-Tier Architectures
ICDCS '02 Proceedings of the 22 nd International Conference on Distributed Computing Systems (ICDCS'02)
Experiences, Strategies, and Challenges in Building Fault-Tolerant CORBA Systems
IEEE Transactions on Computers
| Hi-index | 0.00 |
The CORBA standard adopted by OMG supports reliability using two orthogonal mechanisms: Replication (by means of FT-CORBA standard) and Transaction (with the aid of OTS standard). Replication represents a roll-forward approach in which a failed request is re-directed into another replica that is alive. On the other hand, transaction represents a roll-back approach in which a system reverts into its last committed state upon any failure. Current researches show that integrating these two approaches is essential in 3-tier systems, wherein the replication protects system processes from failures in the middle tier, and the transaction concept ensures the data consistency in the data tier. All proposed methods for reconciling these two concepts are unanimous that the transaction approach suffers from poor performance due to the use of two-phase commit protocol. In this paper we introduce a new replication-aware transaction model based on replicated objects. This kind of transaction can jump over the failures that the replicas come across without rolling the whole transaction back (we call it roll-over). Instead, the failed objects would be removed from the replica list and re-created somewhere else if needed. Implementation results of our model show better transaction throughput in comparison with known approaches.