DBMS > Apache Phoenix vs. Google BigQuery vs. Hive vs. MySQL vs. SiriDB

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. Hive vs. MySQL vs. SiriDB

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Widely used open source RDBMS

Open Source Time Series DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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	59.76
Rank	#18	Overall
	#12	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Website

phoenix.apache.org

cloud.google.com/bigquery

hive.apache.org

www.mysql.com

siridb.com

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

cwiki.apache.org/confluence/display/Hive/Home

dev.mysql.com/doc

docs.siridb.com

Developer

Apache Software Foundation

Google

Apache Software Foundation

initially developed by Facebook

Oracle

since 2010, originally MySQL AB, then Sun

Cesbit

Initial release

2014

2010

2012

1995

2017

Current release

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

3.1.3, April 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

Linux
Unix
Windows

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

yes

with proprietary extensions

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 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)

Access rights for users, groups and roles

Users with fine-grained authorization concept

no user groups or roles

simple rights management via user accounts

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.