DBMS > Google Cloud Bigtable vs. Google Cloud Firestore vs. Google Cloud Spanner vs. Percona Server for MongoDB vs. SQLite

System Properties Comparison Google Cloud Bigtable vs. Google Cloud Firestore vs. Google Cloud Spanner vs. Percona Server for MongoDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store
Wide column store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	2.89
Rank	#105	Overall
	#53	Relational DBMS

Score	0.55
Rank	#253	Overall
	#39	Document stores

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

cloud.google.com/bigtable

firebase.google.com/products/firestore

cloud.google.com/spanner

www.percona.com/mongodb/software/percona-server-for-mongodb

www.sqlite.org

Technical documentation

cloud.google.com/bigtable/docs

firebase.google.com/docs/firestore

cloud.google.com/spanner/docs

docs.percona.com/percona-distribution-for-mongodb

www.sqlite.org/docs.html

Developer

Google

Percona

Dwayne Richard Hipp

Initial release

2015

2017

2015

2000

Current release

3.4.10-2.10, November 2017

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

hosted

Linux

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Go
Java
JavaScript (Node.js)
Python

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

JavaScript

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication

Multi-source replication with 3 replicas for regional instances.

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic single-row operations

yes

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

yes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users and roles

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.