Google Cloud Spanner vs YugabyteDB

Overview

Google Cloud Spanner

Stacks57

Followers117

Votes3

GitHub Stars2.0K

Forks1.1K

YugabyteDB

Stacks50

Followers114

Votes1

GitHub Stars9.9K

Forks1.2K

Google Cloud Spanner vs YugabyteDB: What are the differences?

Architecture: Google Cloud Spanner is a globally distributed database service that provides strong consistency and horizontal scalability, while YugabyteDB is an open-source distributed SQL database built on a similar architecture but with a focus on linear scalability and multi-cloud deployment.
Consistency Model: Google Cloud Spanner uses a strict external consistency model, ensuring that all transactions are serializable, whereas YugabyteDB allows users to choose between strong consistency, eventual consistency, or tunable consistency levels based on their specific requirements.
Deployment Flexibility: Google Cloud Spanner is a fully managed service offered by Google Cloud Platform, with limited deployment options, while YugabyteDB can be deployed on-premises, in the cloud, across multiple clouds, or in a hybrid environment, providing more deployment flexibility for users.
Pricing Model: Google Cloud Spanner follows a pricing model based on resource consumption, including storage, compute, and networking costs, while YugabyteDB is an open-source database that is free to use, with optional commercial support and enterprise features available for purchase.
Native Capabilities: Google Cloud Spanner natively supports relational data model with SQL queries, while YugabyteDB offers native support for SQL and NoSQL data models, providing users with more versatility in handling various types of data within the same database.
Development Community: YugabyteDB has a strong open-source community supporting its development and contributing to its enhancements, while Google Cloud Spanner, being a proprietary service, relies on the Google Cloud team for updates and improvements.

In Summary, Google Cloud Spanner and YugabyteDB differ in their architecture, consistency model, deployment flexibility, pricing model, native capabilities, and development community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

Google Cloud Spanner	YugabyteDB
It is a globally distributed database service that gives developers a production-ready storage solution. It provides key features such as global transactions, strongly consistent reads, and automatic multi-site replication and failover.	An open-source, high-performance, distributed SQL database built for resilience and scale. Re-uses the upper half of PostgreSQL to offer advanced RDBMS features, architected to be fully distributed like Google Spanner.
Global transactions; Strongly consistent reads; Automatic multi-site replication; Failover.	Resilience; High Performance; Scalability; Enterprise Grade; Cloud-native; Kubernetes; PostgreSQL-compatible; Geo-Distributed; Hybrid Cloud
Statistics
GitHub Stars 2.0K	GitHub Stars 9.9K
GitHub Forks 1.1K	GitHub Forks 1.2K
Stacks 57	Stacks 50
Followers 117	Followers 114
Votes 3	Votes 1
Pros & Cons
Pros 1 Scalable 1 Horizontal scaling 1 Strongly consistent	Pros 1 Compatible with the result of pg_dump
Integrations
MySQL PostgreSQL MongoDB SQLite	Golang PHP Java Python Spring Boot Apache Spark Node.js C# Kubernetes Ruby

What are some alternatives to Google Cloud Spanner, YugabyteDB?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap vs Materialize

Django vs Laravel vs Node.js

Bootstrap vs Foundation vs Material UI

Node.js vs Spring-Boot

Flyway vs Liquibase

Google Cloud Spanner vs YugabyteDB: What are the differences?

Architecture: Google Cloud Spanner is a globally distributed database service that provides strong consistency and horizontal scalability, while YugabyteDB is an open-source distributed SQL database built on a similar architecture but with a focus on linear scalability and multi-cloud deployment.
Consistency Model: Google Cloud Spanner uses a strict external consistency model, ensuring that all transactions are serializable, whereas YugabyteDB allows users to choose between strong consistency, eventual consistency, or tunable consistency levels based on their specific requirements.
Deployment Flexibility: Google Cloud Spanner is a fully managed service offered by Google Cloud Platform, with limited deployment options, while YugabyteDB can be deployed on-premises, in the cloud, across multiple clouds, or in a hybrid environment, providing more deployment flexibility for users.
Pricing Model: Google Cloud Spanner follows a pricing model based on resource consumption, including storage, compute, and networking costs, while YugabyteDB is an open-source database that is free to use, with optional commercial support and enterprise features available for purchase.
Native Capabilities: Google Cloud Spanner natively supports relational data model with SQL queries, while YugabyteDB offers native support for SQL and NoSQL data models, providing users with more versatility in handling various types of data within the same database.
Development Community: YugabyteDB has a strong open-source community supporting its development and contributing to its enhancements, while Google Cloud Spanner, being a proprietary service, relies on the Google Cloud team for updates and improvements.

In Summary, Google Cloud Spanner and YugabyteDB differ in their architecture, consistency model, deployment flexibility, pricing model, native capabilities, and development community support.