DBMS > Amazon DocumentDB vs. Google BigQuery vs. HEAVY.AI vs. Quasardb vs. TimesTen

System Properties Comparison Amazon DocumentDB vs. Google BigQuery vs. HEAVY.AI vs. Quasardb vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service with append-only tables

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Distributed, high-performance timeseries database

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

aws.amazon.com/documentdb

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

quasar.ai

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

aws.amazon.com/documentdb/resources

cloud.google.com/bigquery/docs

docs.heavy.ai

doc.quasar.ai/master

docs.oracle.com/database/timesten-18.1

Developer

Google

HEAVY.AI, Inc.

quasardb

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2019

2010

2016

2009

1998

Current release

5.10, January 2022

3.14.1, January 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

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++ and CUDA

C++

Server operating systems

hosted

Linux

BSD
Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

in JavaScript

PL/SQL

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication

Source-replica replication with selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Access rights for users and roles

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

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.