DBMS > Apache Phoenix vs. Google BigQuery vs. H2 vs. Prometheus vs. XTDB

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. H2 vs. Prometheus vs. XTDB

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

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

Open-source Time Series DBMS and monitoring system

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

phoenix.apache.org

cloud.google.com/bigquery

www.h2database.com

prometheus.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

www.h2database.com/html/main.html

prometheus.io/docs

www.xtdb.com/docs

Developer

Apache Software Foundation

Google

Thomas Mueller

Juxt Ltd.

Initial release

2014

2010

2005

2015

2019

Current release

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

2.2.220, July 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

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

Open Source

Apache 2.0

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.

Implementation language

Java

Clojure

Server operating systems

Linux
Unix
Windows

hosted

All OS with a Java VM

Linux
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes, extensible-data-notation format

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 of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC

RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Java Stored Procedures and User-Defined Functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

yes

by Federation

yes, each node contains all data

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

none

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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)

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.