IEEE Transactions on Dependable and Secure Computing
In this paper, we describe a software infrastructure that unifies transactions and replication in three-tier architectures and provides data consistency and high availability for enterprise applications. The infrastructure uses transactions based on the CORBA object transaction service to protect the application data in databases on stable storage, using a roll-backward recovery strategy, and replication based on the fault tolerant CORBA standard to protect the middle-tier servers, using a roll-forward recovery strategy. The infrastructure replicates the middle-tier servers to protect the application business logic processing. In addition, it replicates the transaction coordinator, which renders the two-phase commit protocol nonblocking and, thus, avoids potentially long service disruptions caused by failure of the coordinator. The infrastructure handles the interactions between the replicated middle-tier servers and the database servers through replicated gateways that prevent duplicate requests from reaching the database servers. It implements automatic client-side failover mechanisms, which guarantee that clients know the outcome of the requests that they have made, and retries aborted transactions automatically on behalf of the clients.
Zhao, Wenbing; Moser, Louise E.; and Melliar-Smith, P. Michael, "Unification of Transactions and Replication in Three-Tier Architectures Based on CORBA" (2005). Electrical Engineering & Computer Science Faculty Publications. 81.
Wenbing, Z., Moser, L. E., & Melliar-Smith, P. M. (2005). Unification of transactions and replication in three-tier architectures based on CORBA. IEEE Transactions on Dependable and Secure Computing, 2, 1, 20-33.
© 2005 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes, creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.