Google Cloud Spanner

YugabyteDB’s sharding, replication and transactions architecture is similar to that of Google Cloud Spanner which is also a globally-distributed CP database with high write availability. Both these databases are based on the design principles outlined in the original Google Spanner paper published in 2012. Note that while Google Cloud Spanner leverages Google’s proprietary (and expensive) network infrastructure, YugabyteDB is designed work on commodity infrastructure used by most enterprise users.

Following blogs highlight how YugabyteDB differs from Google Cloud Spanner.

• Distributed PostgreSQL on a Google Spanner Architecture – Storage Layer

• Distributed PostgreSQL on a Google Spanner Architecture – Query Layer

• Yes We Can! Distributed ACID Transactions with High Performance

• Practical Tradeoffs in Google Cloud Spanner, Azure Cosmos DB and YugabyteDB

• New to Google Cloud Databases? 5 Areas of Confusion That You Better Be Aware of

Following blogs highlight how YugabyteDB works as an open source, cloud native Spanner derivative.

• Rise of Globally Distributed SQL Databases – Redefining Transactional Stores for Cloud Native Era

• Implementing Distributed Transactions the Google Way: Percolator vs. Spanner

• Google Spanner vs. Calvin: Is There a Clear Winner in the Battle for Global Consistency at Scale?