DBMS > Apache Phoenix vs. Google BigQuery vs. IBM Db2 warehouse vs. SQream DB vs. Tarantool

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. IBM Db2 warehouse vs. SQream DB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Large scale data warehouse service with append-only tables

Cloud-based data warehousing service

a GPU-based, columnar RDBMS for big data analytics workloads

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

phoenix.apache.org

cloud.google.com/bigquery

www.ibm.com/products/db2/warehouse

sqream.com

www.tarantool.io

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

docs.sqream.com

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Google

IBM

SQream Technologies

Initial release

2014

2010

2014

2017

2008

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

2022.1.6, December 2022

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++, CUDA, Haskell, Java, Scala

C and C++

Server operating systems

Linux
Unix
Windows

hosted

Linux

BSD
Linux
macOS

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

.Net
JDBC
ODBC

Open binary protocol

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in JavaScript

PL/SQL, SQL PL

user defined functions in Python

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal and vertical partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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 Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.