DBMS > Google BigQuery vs. HEAVY.AI vs. IBM Cloudant vs. Kinetica vs. LevelDB

System Properties Comparison Google BigQuery vs. HEAVY.AI vs. IBM Cloudant vs. Kinetica vs. LevelDB

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

Fully vectorized database across both GPUs and CPUs

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Primary database model

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Website

cloud.google.com/bigquery

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

www.ibm.com/products/cloudant

www.kinetica.com

github.com/google/leveldb

Technical documentation

cloud.google.com/bigquery/docs

docs.heavy.ai

cloud.ibm.com/docs/Cloudant

docs.kinetica.com

github.com/google/leveldb/blob/main/doc/index.md

Developer

Google

HEAVY.AI, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Kinetica

Google

Initial release

2010

2016

2010

2012

2011

Current release

5.10, January 2022

7.1, August 2021

1.23, February 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

BSD

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

Erlang

C, C++

C++

Server operating systems

hosted

Linux

hosted

Linux

Illumos
Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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 DML and DDL statements

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

C++
Java
JavaScript (Node.js)
Python

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Since BigQuery is designed for querying data

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

In-memory capabilities

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

yes

GPU vRAM or System RAM

User concepts

Access control

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

Access rights for users can be defined per database

Access rights for users and roles on table level

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.