DBMS > Google BigQuery vs. Google Cloud Datastore vs. H2 vs. Microsoft Azure SQL Database vs. TinkerGraph

System Properties Comparison Google BigQuery vs. Google Cloud Datastore vs. H2 vs. Microsoft Azure SQL Database vs. TinkerGraph

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Database as a Service offering with high compatibility to Microsoft SQL Server

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial 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	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	0.13
Rank	#345	Overall
	#35	Graph DBMS

Website

cloud.google.com/bigquery

cloud.google.com/datastore

www.h2database.com

azure.microsoft.com/en-us/products/azure-sql/database

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

docs.microsoft.com/en-us/azure/azure-sql

Developer

Google

Thomas Mueller

Microsoft

Initial release

2010

2008

2005

2010

2009

Current release

2.2.220, July 2023

V12

License

Commercial or Open Source

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

commercial

Open Source

Apache 2.0

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

Java

C++

Java

Server operating systems

hosted

All OS with a Java VM

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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.

yes

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

JDBC
ODBC

ADO.NET
JDBC
ODBC

TinkerPop 3

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Java

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

Java Stored Procedures and User-Defined Functions

Transact SQL

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

With clustering: 2 database servers on different computers operate on identical copies of a database

yes, with always 3 replicas available

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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

none

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

optional

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)

fine grained access rights according to SQL-standard

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.