Spanner
ACM Transactions on Computer Systems2013Vol. 31(3), pp. 1–22
Citations Over TimeTop 1% of 2013 papers
James C. Corbett, Jay B. Dean, Michael Epstein, Andrew Fikes, Christopher Frost, J. J. Furman, Sanjay Ghemawat, Andrey Gubarev, Christopher Heiser, Peter Hochschild, Wilson C. Hsieh, Sebastian Kanthak, Eugene Kogan, Hongyi Li, Alexander Lloyd, Sergey Melnik, David Mwaura, David F. Nagle, Sean Quinlan, Rajesh Rao, Lindsay Rolig, Yasushi Saitō, Michal Szymaniak, Christopher M. Taylor, Ruth Wang, Dale Woodford
Abstract
Spanner is Google’s scalable, multiversion, globally distributed, and synchronously replicated database. It is the first system to distribute data at global scale and support externally-consistent distributed transactions. This article describes how Spanner is structured, its feature set, the rationale underlying various design decisions, and a novel time API that exposes clock uncertainty. This API and its implementation are critical to supporting external consistency and a variety of powerful features: nonblocking reads in the past, lock-free snapshot transactions, and atomic schema changes, across all of Spanner.
Related Papers
- → Quality-of-Service for Consistency of Data Geo-replication in Cloud Computing(2012)21 cited
- Consistency Management Strategies for Data Replication in MANET(2011)
- → Flexible Consistency for Distributed Storage Systems(2017)1 cited
- → Data Consistency as a Service (DCaaS)(2012)
- → Consistency in Distributed Data Stores(2016)