Deuteronomy: Transaction support for cloud data

Justin J. Levandoski; David Lomet; Mohamed F Mokbel; Kevin Keliang Zhao

Deuteronomy: Transaction support for cloud data

Justin J. Levandoski, David Lomet, Mohamed F Mokbel, Kevin Keliang Zhao

Computer Science and Engineering

Research output: Contribution to conference › Paper › peer-review

61 Scopus citations

Abstract

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)
Pages	123-133
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

Other	5th Biennial Conference on Innovative Data Systems Research, CIDR 2011
Country	United States
City	Asilomar, CA
Period	1/9/11 → 1/12/11

Fingerprint Dive into the research topics of 'Deuteronomy: Transaction support for cloud data'. Together they form a unique fingerprint.

Cite this

@conference{7d722e1df21f4e8ab4468c3ce4761a44,

title = "Deuteronomy: Transaction support for cloud data",

abstract = "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.",

author = "Levandoski, {Justin J.} and David Lomet and Mokbel, {Mohamed F} and Zhao, {Kevin Keliang}",

year = "2011",

month = oct,

day = "11",

language = "English (US)",

pages = "123--133",

note = "5th Biennial Conference on Innovative Data Systems Research, CIDR 2011 ; Conference date: 09-01-2011 Through 12-01-2011",

}

TY - CONF

T1 - Deuteronomy

T2 - 5th Biennial Conference on Innovative Data Systems Research, CIDR 2011

AU - Levandoski, Justin J.

AU - Lomet, David

AU - Mokbel, Mohamed F

AU - Zhao, Kevin Keliang

PY - 2011/10/11

Y1 - 2011/10/11

N2 - 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.

AB - 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.

UR - http://www.scopus.com/inward/record.url?scp=80053544112&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=80053544112&partnerID=8YFLogxK

M3 - Paper

AN - SCOPUS:80053544112

SP - 123

EP - 133

Y2 - 9 January 2011 through 12 January 2011

ER -

Deuteronomy: Transaction support for cloud data

Abstract

Other

Other files and links

Cite this