Spanner (database)

Spanner is a NewSQL database developed by Google.[1] Spanner is a globally distributed database service and storage solution. It provides features such as global transactions, strongly consistent reads, and automatic multi-site replication and failover.

Cloud Spanner Logo
Cloud Spanner Booth at Google Cloud Summit

Features

Spanner stores large amounts of mutable structured data. Spanner allows users to perform arbitrary queries using SQL with relational data while maintaining strong consistency and high availability for that data with synchronous replication.

Key features of Spanner:

  • Transactions can be applied across rows, columns, tables, and databases within a Spanner universe.
  • Clients can control the replication and placement of data using automatic multi-site replication and failover.
  • Replication is synchronous and strongly consistent.
  • Reads are strongly consistent and data is versioned to allow for stale reads: clients can read previous versions of data, subject to garbage collection windows.
  • Supports a native SQL interface for reading and writing data.

History

Spanner joined the Google platform in February 2017.[2] It is available as part of Google Cloud Platform.[3]

Spanner's SQL capability was added in 2017 and documented in a SIGMOD 2017 paper [4]

Architecture

Spanner uses the Paxos algorithm as part of its operation to shard (partition) data across hundreds of servers.[1] It makes heavy use of hardware-assisted clock synchronization using GPS clocks and atomic clocks to ensure global consistency.[1]

Google's F1 SQL database management system (DBMS) is built on top of Spanner,[5] replacing Google's custom MySQL variant.[6]

References

  1. Corbett et al. 2012.
  2. Clark, Jack (September 18, 2012). "Google reveals Spanner, the database tech that can span the planet". ZDNet. Retrieved 2012-09-21.
  3. Srivastava, Deepti (2017-02-14). "Introducing Cloud Spanner: a global database service for mission-critical applications".
  4. "Spanner: Becoming a SQL System".
  5. Shute et al. 2012.
  6. Shute et al. 2012, p. 19: ‘Summary: We've moved a large and critical application suite from MySQL to F1.’

Bibliography

  • Corbett, James C; Dean, Jeffrey; Epstein, Michael; Fikes, Andrew; Frost, Christopher; Furman, JJ; Ghemawat, Sanjay; Gubarev, Andrey; Heiser, Christopher; Hochschild, Peter; Hsieh, Wilson; Kanthak, Sebastian; Kogan, Eugene; Li, Hongyi; Lloyd, Alexander; Melnik, Sergey; Mwaura, David; Nagle, David; Quinlan, Sean; Rao, Rajesh; Rolig, Lindsay; Saito, Yasushi; Szymaniak, Michal; Taylor, Christopher; Wang, Ruth; Woodford, Dale, "Spanner: Google's Globally-Distributed Database" (PDF), Proceedings of OSDI 2012, Google, retrieved 18 September 2012.
  • Date, Christopher ‘Chris’ J (2004), "6. Relations, Part II. The Relational Model", An Introduction to Database Systems (8th ed.), Addison Wesley, ISBN 978-0-32119784-9.
  • Shute, Jeffrey ‘Jeff’; Oancea, Mircea; Ellner, Stephan; Handy, Benjamin ‘Ben’; Rollins, Eric; Samwel, Bart; Vingralek, Radek; Whipkey, Chad; Chen, Xin; Jegerlehner, Beat; Littlefield, Kyle; Tong, Phoenix (2012), "F1 — the Fault-Tolerant Distributed RDBMS Supporting Google's Ad Business", Research (presentation), Sigmod: Google.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.