The Deuteronomy system supports efficient and scalable ACID transactions in the cloud by decomposing functions of a database storage engine kernel into: (a) a transactional component (TC) that manages transactions and their "logical" concurrency control and undo/redo recovery, but knows nothing about physical data location and (b) a data component (DC) that maintains a data cache and uses access methods to support a record-oriented interface with atomic operations, but knows nothing about transactions. The Deuteronomy TC can be applied to data anywhere (in the cloud, local, etc.) with a variety of deployments for both the TC and DC. In this paper, we describe the architecture of our TC, and the considerations that led to it. Preliminary experiments using an adapted TPC-W workload show good performance supporting ACID transactions for a wide range of DC latencies.
|Original language||English (US)|
|Number of pages||11|
|State||Published - Oct 11 2011|
|Event||5th Biennial Conference on Innovative Data Systems Research, CIDR 2011 - Asilomar, CA, United States|
Duration: Jan 9 2011 → Jan 12 2011
|Other||5th Biennial Conference on Innovative Data Systems Research, CIDR 2011|
|Period||1/9/11 → 1/12/11|