TY - GEN
T1 - Depot
T2 - 9th USENIX Symposium on Operating Systems Design and Implementation, OSDI 2010
AU - Mahajan, Prince
AU - Setty, Srinath
AU - Lee, Sangmin
AU - Clement, Allen
AU - Alvisi, Lorenzo
AU - Dahlin, Mike
AU - Walfish, Michael
N1 - Funding Information:
Insightful comments by Marcos K. Aguilera, Hari Bal-akrishnan, Brad Karp, David Mazières, Arun Seehra, Jessica Wilson, the anonymous reviewers, and our shepherd, Michael Freedman, improved this paper. The Emulab staff was a great help, as always. This work was supported by ONR grant N00014-09-10757, AFOSR grant FA9550-10-1-0073, and NSF grant CNS-0720649.
PY - 2019
Y1 - 2019
N2 - The paper describes the design, implementation, and evaluation of Depot, a cloud storage system that minimizes trust assumptions. Depot tolerates buggy or malicious behavior by any number of clients or servers, yet it provides safety and liveness guarantees to correct clients. Depot provides these guarantees using a two-layer architecture. First, Depot ensures that the updates observed by correct nodes are consistently ordered under Fork-Join-Causal consistency (FJC). FJC is a slight weakening of causal consistency that can be both safe and live despite faulty nodes. Second, Depot implements protocols that use this consistent ordering of updates to provide other desirable consistency, staleness, durability, and recovery properties. Our evaluation suggests that the costs of these guarantees are modest and that Depot can tolerate faults and maintain good availability, latency, overhead, and staleness even when significant faults occur.
AB - The paper describes the design, implementation, and evaluation of Depot, a cloud storage system that minimizes trust assumptions. Depot tolerates buggy or malicious behavior by any number of clients or servers, yet it provides safety and liveness guarantees to correct clients. Depot provides these guarantees using a two-layer architecture. First, Depot ensures that the updates observed by correct nodes are consistently ordered under Fork-Join-Causal consistency (FJC). FJC is a slight weakening of causal consistency that can be both safe and live despite faulty nodes. Second, Depot implements protocols that use this consistent ordering of updates to provide other desirable consistency, staleness, durability, and recovery properties. Our evaluation suggests that the costs of these guarantees are modest and that Depot can tolerate faults and maintain good availability, latency, overhead, and staleness even when significant faults occur.
UR - http://www.scopus.com/inward/record.url?scp=85076918673&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85076918673&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:85076918673
T3 - Proceedings of the 9th USENIX Symposium on Operating Systems Design and Implementation, OSDI 2010
SP - 307
EP - 322
BT - Proceedings of the 9th USENIX Symposium on Operating Systems Design and Implementation, OSDI 2010
PB - USENIX Association
Y2 - 4 October 2010 through 6 October 2010
ER -