DBMS > Google BigQuery vs. Google Cloud Datastore vs. RethinkDB vs. SpatiaLite

System Properties Comparison Google BigQuery vs. Google Cloud Datastore vs. RethinkDB vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Spatial extension of SQLite

Primary database model

Relational DBMS

Document store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

cloud.google.com/bigquery

cloud.google.com/datastore

rethinkdb.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

rethinkdb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Google

The Linux Foundation

since July 2017

Alessandro Furieri

Initial release

2010

2008

2009

2008

Current release

2.4.1, August 2020

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

string, binary, float, bool, date, geometry

yes

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

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

range based

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

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

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

yes

users and table-level permissions

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.