DBMS > 4D vs. Apache Phoenix vs. Google BigQuery vs. HBase vs. KairosDB

System Properties Comparison 4D vs. Apache Phoenix vs. Google BigQuery vs. HBase vs. KairosDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Large scale data warehouse service with append-only tables

Wide-column store based on Apache Hadoop and on concepts of BigTable

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Relational DBMS

Wide column store

Time Series DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Website

www.4d.com

phoenix.apache.org

cloud.google.com/bigquery

hbase.apache.org

github.com/kairosdb/kairosdb

Technical documentation

developer.4d.com

phoenix.apache.org

cloud.google.com/bigquery/docs

hbase.apache.org/book.html

kairosdb.github.io

Developer

4D, Inc

Apache Software Foundation

Google

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

1984

2014

2010

2008

2013

Current release

v20, April 2023

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

2.3.4, January 2021

1.2.2, November 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache version 2

Open Source

Apache 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

OS X
Windows

Linux
Unix
Windows

hosted

Linux
Unix
Windows

using Cygwin

Linux
OS X
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC

RESTful HTTP/JSON API

Java API
RESTful HTTP API
Thrift

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

4D proprietary IDE
PHP

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Groovy
Java
PHP
Python
Scala

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

Single row ACID (across millions of columns)

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

Users and groups

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

simple password-based access control

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.