DBMS > Apache Phoenix vs. Google BigQuery vs. InfinityDB vs. MonetDB

System Properties Comparison Apache Phoenix vs. Google BigQuery vs. InfinityDB vs. MonetDB

Please select another system to include it in the comparison.

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

A Java embedded Key-Value Store which extends the Java Map interface

A relational database management system that stores data in columns

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
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	0.00
Rank	#378	Overall
	#57	Key-value stores

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Website

phoenix.apache.org

cloud.google.com/bigquery

boilerbay.com

www.monetdb.org

Technical documentation

phoenix.apache.org

cloud.google.com/bigquery/docs

boilerbay.com/infinitydb/manual

www.monetdb.org/Documentation

Developer

Apache Software Foundation

Google

Boiler Bay Inc.

MonetDB BV

Initial release

2014

2010

2002

2004

Current release

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

4.0

Dec2023 (11.49), December 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Mozilla Public License 2.0

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

Server operating systems

Linux
Unix
Windows

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

SQL

Support of SQL

yes

SQL 2003 with some extensions

APIs and other access methods

JDBC

RESTful HTTP/JSON API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Supported programming languages

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes, in SQL, C, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding via remote tables

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication available in experimental status

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

READ-COMMITTED or SERIALIZED

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

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)

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.